-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Improved handling of configuration values #62
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is this a new feature request?
Wanted change
Add the ability to specify configuration variables w/o hand editting configuration.py.
This may relate to #59
Reason for change
I manage my containers with CM (puppet) and strongly dislike having to hand edit files in a container. I haven't found any tools that allow an easy way to update python configuration files.
Proposed code change
I tried to specify another configuration script (config.py) which reads configuration.py and also reads a yaml file. But could not get that to work properly. I'm probably missing some subtle issue with python importlib.
What I ended up doing that worked was appending the following code to the end of configuration.py and then writing my configuration into a yaml file called
config.yaml
. This allows anything set in configuration.py to be used, but values inconfig.yaml
override it.This could be expanded to write one YAML file for data passed in from the environment and another for additional configuration written by the user.
Thoughts?
The text was updated successfully, but these errors were encountered: