Actions
Story #5290
closed
As a plugin writer, I can provide all of my settings with their defaults in one place.
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 58
Quarter:
Description
Problem¶
Currently pulp_ansible has several settings. There isn't a consolidated way currently for dynaconf to overlay settings from the pulp_ansible codebase onto the settings file provided by pulpcore.app.settings
Solution¶
1. Document in the plugin writer's guide a convention that settings should live in pluginname.app.settings
2. Then here you build the list of python paths to the settings file.
3. Then here you have dynaconf load those settings.
This needs to come with documentation for plugin writers and a release note in pulpcore-plugin, even though the changes will mostly occur in pulpcore.
Actions
.
Add load of plugin default settings.
{plugin_name}/app/settings.py/etc/pulp/settings.pyPULP_RPM,FILE,ANSIBLEetc...example:
ANSIBLE_SOMEKEY = 'value'on settings.py can be overriden viaexport PULP_ANSIBLE_SOMEKEY='othervalue'closes #5290