@boedy Thanks for sharing your use-case! As you mentioned, shared config values like these would work great in a dedicated project for them that are then referenced cross-project. Once you have that setup, if your ops team needed access to see what values were set, they could run doppler secrets using the access token of the deployment environment. Alternately, if you didn’t want them to see the actual secret values vs configuration values, then you could provide them access to the shared project and they could run doppler secrets against that (or just view it in the dashboard) to see what’s in use.
Would that work for you? Is there a particular reason you find including those values directly in git desireable?
