@spencergibb yeah, but what about "many git repos for one application"? Like "repo with passwords" and "repo with non-sensitive config available for developers to modify values like TTLs, timeouts, etc"?
(I.e. you're expected to encrypt the sensitive values. If developers wanted to I guess they could break the app in production by putting in an invalid secret. But they can't learn the secrets if they don't have the key.)