Actions
Story #5435
closedAs a pulp-operator user, I can add arbitrary settings to settings.py
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 61
Quarter:
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
Actions
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