Story #5435
closed
As a pulp-operator user, I can add arbitrary settings to settings.py
0%
Description
The Docker plugin is adding a new setting, which cannot be set without a change to pulp-operator.
When travis used ansible-pulp to install, arbitrary settings could be added with an ansible variable `pulp_settings`.
https://github.com/pulp/pulp_docker/blob/master/.travis/playbook.yml#L27-L33
All values in pulp_settings (after being merged with the default settings) are added to settings.py in the jinja template.
https://github.com/pulp/ansible-pulp/blob/master/roles/pulp/templates/settings.py.j2
Something similar could be added to the operator https://github.com/pulp/pulp-operator/blob/fd6b7d92f057d369cd11489aa6e02cdc5a0000f4/roles/pulp-api/templates/pulp-server.config-map.yaml#L28-L30
Updated by amacdona@redhat.com about 3 years ago
We'll need to test if we can use an arbitrary hash tables for ansible-operator custom resources, and have them become ansible hash table variables / jinja2 hash table variables.
Updated by fao89 about 3 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Updated by dkliban@redhat.com about 3 years ago
- Sprint set to Sprint 60
This feature is needed to roll out containers to all the plugins. This includes pulp_docker and pulp_ansible.
Updated by dkliban@redhat.com about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Added by dkliban@redhat.com about 3 years ago
Updated by dkliban@redhat.com about 3 years ago
- Status changed from ASSIGNED to MODIFIED
Updated by bmbouter almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Allows user to specify all pulp_settings
This patch introduces a 'pulp_settings' config and moves the 'content_host' setting under it.
re: #5435 https://pulp.plan.io/issues/5435