Open osterman opened 5 years ago
Ultimately, we want to achieve DRYness, but with clarity on when to use what.
.tfvars is the most intuitive, coming from the world of terraform.
direnv has been brilliant in projects where my directory structure has had a strong correlation to the project architecture (both logical and/or infrastructure)
I want to explore using docker file env parameters more, possibly with a more multi image layer approach.
I want to explore using docker file env parameters more, possibly with a more multi image layer approach.
The biggest downside with this is needing to rebuild the image, especially if using envs-inside-of-envs. We do this a lot today, but the impact on development is less desirable.
what
why
examples
Here are a few approaches:
chamber
envconsul
with HashiCorpvault
Dockerfile
withENV
parameters.tfvar
files (with or withoutterragrunt
)direnv
with.envrc
files