Welcome to dynaconf Discussions!

[rochacbruno]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[rujutashinde]

Hello @rochacbruno
I am trying to use dynaconf for my project, for my usecase i wanted to look at my config file(ini file) as well as env variables set, and if env variables are set, they should hold precedence. If the config file does not have an entry for a specific section, and if env variable is set , that should get used.
I was able to use dynaconf and get the env variables , but i could not find an example where we can compare them to the ones set within the config file. Is this an usecase you support? Could you point me to an example?
Appreciate the help!
Thanks,
Rujuta

[rochacbruno]

Hi @rujutashinde

Dynaconf execute loaders in order and latest overrides previous loader, so in your case, dynaconf will read all the variables in your .ini file, then, it will load everything from environment variables ans override those using same name.

I can't clearly understand your use case, what do you need to compare? do you need to know where a variable or value came from?

[rujutashinde]

Thank you @rochacbruno for taking time to answer the question. Following is my use case:

I have a config file named teflo.cfg which contains my configuration in a ini format, e.g below

[defaults]
log_level=info
workspace=.
data_folder=.teflo

[orchestrator:ansible]
log_remove=True
verbosity=v

[orchestrator:puppet]
log_remove=True
verbosity=v

So far I was using configparser to parse this file and get what i need. Now I wanted to add a functionality to my project where i can declare environmental variables like export TEFLO_ORCHESTRATOR_ANSIBLE_VERBOSITY=vvv. So now my project should use the values from the teflo.cfg file , but only the values where env variables are declared should be overridden. In the end , project should have orchestrator_ansible_log_remove as true and orchestrator_ansible_verbosity as vvv instead of v declared in teflo.cfg. Also other values from the teflo.cfg should be available.

When using dynaconf, I was able to get the env variables declared as TEFLO_<>. but i could not get the remaining keys and values from the teflo.cfg which i was using as settings_file.

When the environment variables override the settings file, do we lose all other variables in the settings file? Can this behavior be customized?
This is what i had below. I realized that .ini extension is something dynaconf needs so i did change the .cfg to .ini while using.

self.dynaconf_settings = Dynaconf(settings_files=["/pat to config file/teflo.cfg"], envvar_prefix="TEFLO", )

[rochacbruno]

@rujutashinde

This is the best I could get to reproduce your use case.

Files: https://gist.github.com/rochacbruno/dc569777b67a242dc368d44f0f71609d

Dynaconf has the concept of environments (same as running modes), your app runs in a single mode at a time, by default it has default, development, production, test

I have used a TOML file, you can use a .ini works almost the same, but toml is more recommended because it allows better data structures.

I have never seen a ini section defined using : like in [orchestrator:ansible], dynaconf can load it, but it becomes a key acessible via settings[orchestrator:ansible] not sure if this is what you are looking for.

alternatives

• It is possible to deactivate the multi environments passing environments=False in that case you can have the keys arranged in the way you prefer.
• You can create a custom loader, to parse the ini file the way you want.

All that is described in http://dynaconf.com

[rujutashinde]

Thank you @rochacbruno . I will look into custom loader and figure out if this works for me. Appreciate your time!

[ASG09]

Hello @rochacbruno,
first of all, great library!
I was working with a django application, and while using the django-crontab library, I've found the following syntax for the settings.py file:

CRONJOBS = [ ('*/5 * * * *', 'myapp.cron.other_scheduled_job', ['arg1', 'arg2'], {'verbose': 0}), ('0 4 * * *', 'django.core.management.call_command', ['clearsessions']), ]

I was wondering, how this piece of setting would look like in a settings.yaml file?

Do you know the yaml syntax for this particular case?

[rochacbruno]

I would try:

---
cronjobs:
  - ['*/5 * * * *', 'myapp.cron.other_scheduled_job', ['arg1', 'arg2'], {'verbose': 0}]
  - ['0 4 * * *', 'django.core.management.call_command', ['clearsessions']] 

I tested the yaml parsing

Not sure if the django-crontab app requires tuples instead of lists, if so, then there is no way yet.

[ASG09]

Thanks for the quick answer @rochacbruno !
Apparently they require tuples for the configuration, I'll test it as lists anyway, but if it doesn't work I can still define it within my settings.py if I'm not mistaken (whilst having the setting.yaml working)