Story #3723
Updated by amacdona@redhat.com over 5 years ago
The pulp3 role will use the "pip module":https://docs.ansible.com/ansible/latest/modules/pip_module.html and will install a plugin generically. It will take the following variables: django_app_label - the app name that Pulp should have its migrations run for. name - The name of a Python library to install or the url of the remote package. As of 2.2 you can supply a list of names. It can take the following types of data: -* * VCS project url- url -* * Local path to project- project * Local or remote source archive virtualenv - An optional path to a virtualenv directory to install into. Defaults to <code>/usr/local/pulpenv</code>. If unset, it will install in the system packages. If set but the virtualenv does not exist, it will be created before installing packages. pulp_user - the user to switch to before installing editable - defualts to no. pulp_data_dir - defaults to '/var/lib/pulp'. It is expected that a plugin will bring in the entire Pulp stack with it when it runs.
.