Project

Profile

Help

Story #5435

As a pulp-operator user, I can add arbitrary settings to settings.py

Added by amacdona@redhat.com about 1 month ago. Updated 21 days ago.

Status:
ASSIGNED
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 60

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

History

#1 Updated by amacdona@redhat.com about 1 month 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.

#2 Updated by fabricio.aguiar about 1 month ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#3 Updated by dkliban@redhat.com 21 days 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.

#4 Updated by dkliban@redhat.com 21 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com

Please register to edit this issue

Also available in: Atom PDF