Loving Doppler, but some projects are becoming un-reviewable past 30 secrets.
Within a local .env file, it can be natural to group keys:
Minimal example
[AZURE BLOB]
AZURE_STORAGE_ACCOUNT_NAME=‘…’
AZURE_STORAGE_ACCOUNT_KEY=‘…’
AZURE_STORAGE_CONNECTION_STRING=‘…’
[SUPABASE]
SUPABASE_URL=‘…’
SUPABASE_PROJECT=‘…’
SUPABASE_SERVICE_ROLE_KEY=‘…’
[SNOWFLAKE - AWS US East]
SNOWFLAKE_USERNAME_AWS_US_EAST=‘…’
SNOWFLAKE_PASSWORD_AWS_US_EAST=‘…’
[SNOWFLAKE - AZURE UK South]
SNOWFLAKE_USERNAME_AZURE_UK_SOUTH=‘…’
SNOWFLAKE_PASSWORD_AZURE_UK_SOUTH=‘…’
[LLMs]
OPENAI_API_KEY=‘…’
GOOGLE_GEMINI_API_KEY=‘…’
GROK_API_KEY=‘…’
OPENROUTER_API_KEY=‘…’
That is reasonably easy to review as a .env file (especially with syntax highlighting), but within Doppler the same secrets would show as
AZURE_STORAGE_ACCOUNT_KEY=‘…’
AZURE_STORAGE_ACCOUNT_NAME=‘…’
AZURE_STORAGE_CONNECTION_STRING=‘…’
GOOGLE_GEMINI_API_KEY=‘…’
GROK_API_KEY=‘…’
OPENAI_API_KEY=‘…’
OPENROUTER_API_KEY=‘…’
SNOWFLAKE_PASSWORD_AWS_US_EAST=‘…’
SNOWFLAKE_PASSWORD_AZURE_UK_SOUTH=‘…’
SNOWFLAKE_USERNAME_AWS_US_EAST=‘…’
SNOWFLAKE_USERNAME_AZURE_UK_SOUTH=‘…’
SUPABASE_PROJECT=‘…’
SUPABASE_SERVICE_ROLE_KEY=‘…’
SUPABASE_URL=‘…’
Still manageable… but much harder. It gets really hard past 100 secrets.
It is an excellent idea actually. After 30 secrets it is really hard to find anything unless explicitly searching with CTRL + F. However not only that but looks, you look at your secrets and it is a plain list without any grouping, spacing or something, just list.
Me, and I guess not only me would be happy if you provided us with some kind of tagging or grouping. You can add tags to secrets and filter by tags. It would be really good to see!
But the best possible solution here would be to divide config into groups so it is viewable still as a list but at the top of it there would be groups, so you can just navigate through groups and see it as a list, also a cool feature.
Unfortunately even prefixing doesn’t help much.
Also would like to see disabling secret deriving. I want to have a project that could have several secret configs that are NOT RELATED TO EACH OTHER.
Imagine we have three configs:
A
B
C
When I add a new secret or delete already existing one, I want my changes to be reflected on config C, so new secrets are suggested to fill and appear as missing, you are warned and you need to add it.
When you touch config B, you can do whatever you want as it is not related to A and C.
Currently this is feasible by dividing into multiple projects but it is not convenient enough.
I want to have just one project where I store secrets for the whole project. They could be not related to each other. For example I have project where I store secrets for K8s, Backend, Frontend and it is really annoying when I add some secrets to K8s config and I’m warned to add those missing secrets to other configs though they are not related to each other
