pulp_ansible provides a few settings to control various features. These settings are settable with dynaconf in various as a regular Pulp setting. See the pulpcore Setting.
The origin, e.g. “http://example.com” that will instruct the client how to find the Pulp API service. This URL is formed in various Galaxy APIs (V1, V2, V3) responses.
This defaults to http on your fqdn, which is usable with the Ansible installer’s default Nginx configuration. So if example.com is your fqdn, this would default to “http://example.com”.
The origin, e.g. “http://example.com” that will instruct the client how to find the Pulp content app. This URL is formed in various Galaxy APIs (V1, V2, V3) responses.
This number determines the amount of concurrent signing processes that can be spawned at one time during a signature task. Increasing this number will generally increase the speed of the task, but will also consume more resources of the worker. Defaults to 10 concurrent processes.
By default the Galaxy V1, V2, and V3 APIs are rooted at “/pulp_ansible/galaxy/<path:path>/api/”, but this is configurable. Specifying GALAXY_API_ROOT will re-root the Galaxy API to a different URL namespace.
The <path:path> must be included, which corresponds to the base_path of an Ansible Distribution. Clients using the Galaxy API will only receive content served by that Ansible Distribution.
Set the distribution base path to be used on the
GALAXY_API_ROOT/default/api/endpoint. By default, this is set to
None, which causes the API to return a 404 on the
The Django URL namespace to be used when generating URLs that are returned by the galaxy APIs. Setting this allows for the galaxy APIs to redirect requests to django URLs in other apps. This defaults to the pulp ansible URL router.