Replies: 1 comment
-
Just found the culprit. Non-secret settings/config should be available first. Otherwise dynaconf skips all secret file settings quietly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Not sure if I'm missing something during configuration, so make the post in discussion instead of issue.
My scenario is simply using dynaconf to load a secret file without other configuration, where path to the secret file is passed into
Dynaconf()
loader in absolute path:Suppose my package is called
my_lib
and already installed:File Structure
root 📁
File content:
config.py
:secrets.yml
:run.py
:Expected Outcome
Actual Outcome
Just as shown above, from documentation (and by default?) content of the YAML secret file should get merged into the (lazy) loader when requested, and
secrets
should become available attribute ofsettings
variable. Did I do anything wrong with the above setup?Beta Was this translation helpful? Give feedback.
All reactions