Earlier quoted context omitted.
It's pretty normal to keep secrets in a dedicated secret store, and then have the service launcher inject them from the secret store into the environment.
normal indeed but not what i'd consider a best practice anymore. we've moved away from any secrets in the env after the typical secrets leak when secrets popped up in some debug logging that hit datadog. we now have a secret cache layer api and the app loads secrets securely at time of use from that api. there's also no secret-0 problem because we use IAM auth when calling the cache. edit: for those wondering, api re…
The Twelve-Factor App (2025)
111–120 of 184 posts
Re: The Twelve-Factor App (2025)
#112Earlier quoted context omitted.
The unwritten assumption in 12 Factor is: the environment is secure . For example, a production system should always have a secure means of setting environment variables. Said another way: If a random dev can change an environment variable in production either directly by logging in or indirectly by pushing code then there is something very very wrong. If the dev is pushing code to production they should not simultan…
> Changing application behavior Configuration changes also change application behavior, otherwise is it really “config”?
Re: The Twelve-Factor App (2025)
#113Earlier quoted context omitted.
Okay so this may sound odd but this is literally my whole life right now... Can you explain why do you feel MFA is painful/unsustainable? How would you fix it?
Personally I hate when I use a passkey but then still get hit with an SMS second factor step. A passkey should be enough, unless I'm changing my recovery email or withdrawing a million dollars or something. Also there's still a lot of really bad UX around passkeys, both by browser/OS vendors and by individual apps, and unimplemented features like sharing. Passkeys are the right thing but they need more work.
Re: The Twelve-Factor App (2025)
#114I can't believe how old this is and I feel like most devs still haven't internalized this which is a shame.
Is it devs that haven't internalized this? Or management? Because I'd love to do this, but I always report to people who demand that everything be done in "a few days".
Re: The Twelve-Factor App (2025)
#115I know that all of this is super relevant, but it's extremely aspirational, and I can pick apart pretty much every one of these factors on how it doesn't fully hold up when it comes to the reality of production applications.
Re: The Twelve-Factor App (2025)
#116Its interesting how this felt so natural and right way to do software. I remember people referencing it as the north star. And then gradually people came close to it but moved past it. Personally I feel that these concepts require to have generalist mindset aka application architect. What we have as of today are lot of product engineers within teams, product managers and management. The product engineers do not alway…
Re: The Twelve-Factor App (2025)
#117Re: The Twelve-Factor App (2025)
#118Re: The Twelve-Factor App (2025)
#1192025?
Re: The Twelve-Factor App (2025)
#120Earlier quoted context omitted.
Confidently wrong. Did you read the source I linked? > The twelve-factor app stores config in environment variables
The vault of the cloud provider would just inject the value of the environment variable securely so it doesn't have to be stored on-disk. What the parent poster wrote isn't wrong.