Environment variables are THE MOST FLEXIBLE configuration strategy ever. Just...
Environment variables are THE MOST FLEXIBLE configuration strategy ever.
Just update your CDK code, the Docker image code. Do get 4 merge requests approved, Change Control Board, deploy to DEV, TEST, STAGE, PROD!
So easy! SO MUCH BETTER THAN A CONSTANT in the source code. GOD NO, we'd have to
Update a .py file, Do get 4 merge requests approved, Change Control Board, deploy to DEV, TEST, STAGE, PROD!
So you can SEE the most important 12th factor is environment variables!
Self-replies
"**The twelve-factor app stores config in *environment variables***. Env vars are easy to change between deploys without changing any code;** unlike config files, there is little chance of them being checked into the code repo accidentally;"
But doctor, the ONLY way to change an environment variable is to change code, the envvars are now CODE!
I mean, if we're going to stay in the past, let's bring back copybooks. They are a huge improvement over storing a stack of Jacquard loom cards underneath the sheep. Copybooks have 100% less sheep shit on them.
Oh, no, I should use AWS Parameter Store values?!
Okay, for OPs to update that they need to... say it with me...
Just update your CDK code, the Docker image code. Do get 4 merge requests approved, Change Control Board, deploy to DEV, TEST, STAGE, PROD!