That would require no secrets. All it takes is a misclick into a .env file.
I’d assume you’re not coding on a production system so your secrets shouldn’t be too hard to revoke, cycle them after your stream and any time you leak them.
Secrets should really be stored in services, not files outside of maybe a single bootstrap file (unless you're working on the secret storage service itself).
I generate my secrets once, send them off to the secrets service, and then my service queries that service. I never see the secrets with my own eyes.
The idea is that you keep the name of the secret, and grant access to the secret manager via roles / policies which are generally open to devs on a subnet for a development environment but locked down in production environments.
I think we're probably agreeing with each other, except I'm not willing to call those things "secret." They're public. If you can plan to properly publicize something, great. But work _hard_ to make sure you're really okay publicizing it.
