Would expanding the scope of this project to allow setting application settings in a project's settings.py by reading from 1Password be worth the time to build?
This is obviously beyond the small use case I initially wrote this for, but I just had this thought and need to capture it so I don't forget.
For our applications I use a combination of an .env.prod file with a list of production runtime settings that each contain an op:// URI reference with a single step in deployment using the op inject command to dynamically load them. Would be nice to do away with that and just rely on some sort of functionality built in to a library.
Would expanding the scope of this project to allow setting application settings in a project's
settings.pyby reading from 1Password be worth the time to build?This is obviously beyond the small use case I initially wrote this for, but I just had this thought and need to capture it so I don't forget.
For our applications I use a combination of an
.env.prodfile with a list of production runtime settings that each contain anop://URI reference with a single step in deployment using theop injectcommand to dynamically load them. Would be nice to do away with that and just rely on some sort of functionality built in to a library.