Replies: 2 comments
-
Currently the custom loaders are not a drop in re-placement for the builtin. As the docs shows, you need to handle file finding, for example. But yes, you can use it to leverage your custom resolvers.
Yes, you can disable core and use only your custom + env_loader with the following settings.
I don't think we can evaluate that for you very accurately. |
Beta Was this translation helpful? Give feedback.
-
@pedro-psb Thank you for your answers and for dynaconf. Will evaulate further if dynaconf suits our needs or not. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm not so activate co-maintainer of the open source project GitLabForm.
We are looking into ways to improve our user experience when it comes to configuration.
I found dynaconf for a thing at work recently (@lfvjimisola) and it was VERY convenient.
However, for GitLabForm we have some special needs in terms of the configuration which is currently YAML only (and it might have to stay that way).
We are contemplating using custom implicit resolvers to allow for generic "tags" (for lack of a better name). We are currently using ruamel (not pyyaml) although they should be equivalent since ruamel is a fork of pyyaml.
Our use-case:
It could be that the combination of custom implicit resolvers and dynaconf does not really work. Still trying to figure that out.
My questions are hopefully quite easy:
dynaconf.loaders.env_loader
)?References:
Kindly,
Jimisola
Beta Was this translation helpful? Give feedback.
All reactions