A utility tool to create .env files
dump-env takes an .env.template file and some optional environmental variables to create a new .env file from these two sources. No external dependencies are used.
Why?
Why do we need such a tool? Well, this tool is very helpful when your CI is building docker (or other) images. Previously we had some complex logic of encrypting and decrypting files, importing secret keys and so on. Now we can just create secret variables for our CI, add some prefix to it, and use dump-env to make our life easier.
Installation
$ pip install dump-env
Quickstart
This quick demo will demonstrate the main and the only purpose of dump-env:
$ dump-env --template=.env.template --prefix='SECRET_ENV_' > .env
This command will:
- take
.env.template - parse its keys and values
- read all the variables from the environment starting with
SECRET_ENV_ - remove this prefix
- mix it all together, environment vars may override ones from the template
- sort keys in alphabetic order
- dump all the keys and values into the
.envfile
Advanced Usage
Multiple prefixes
$ dump-env -t .env.template -p 'SECRET_ENV_' -p 'ANOTHER_SECRET_ENV_' > .env
This command will do pretty much the same thing as with one prefix. But, it will replace multiple prefixes. Further prefixes always replace previous ones if they are the same. For example:
$ export SECRET_TOKEN='very secret string'
$ export SECRET_ANSWER='13'
$ export ANOTHER_SECRET_ENV_ANSWER='42'
$ export ANOTHER_SECRET_ENV_VALUE='0'
$ dump-env -p SECRET_ -p ANOTHER_SECRET_ENV_
ANSWER=42
TOKEN=very secret string
VALUE=0
Strict env variables
In case you want to be sure that YOUR_VAR exists in your environment when dumping, you can use --strict flag:
$ dump-env --strict YOUR_VAR -p YOUR_
Missing env vars: YOUR_VAR
Oups! We forgot to create it! Now this will work:
$ export YOUR_VAR='abc'
$ dump-env --strict YOUR_VAR -p YOUR_
VAR=abc
Any number of --strict flags can be provided. No more forgotten template overrides or missing env vars!
Source templates
You can use an env template as a source template by using the -s or --source argument. This will restrict any non-prefixed variables found in the environment to only those already defined in your template.
$ cat template.env
ANSWER=13
TOKEN=very secret string
VALUE=0
$ export ANSWER='42'
$ dump-env --source=template.env
ANSWER=42
TOKEN=very secret string
VALUE=0
You can still also use prefixes to add extra variables from the environment
$ export EXTRA_VAR='foo'
$ dump-env -s template.env -p EXTRA_
ANSWER=13
TOKEN=very secret string
VALUE=0
VAR=foo
Strict Source
Using the --strict-source flag has the same effect as defining a --strict flag for every variable defined in the source template.
$ export ANSWER='42'
$ dump-env -s template.env --strict-source
Missing env vars: TOKEN, VALUE
Creating secret variables in some CIs
Real-world usages
Projects that use this tool in production:
Related
You might also be interested in:
2 Apr 20, 2022
3 Jan 30, 2022
11 May 22, 2022
4.6k Jan 06, 2023
1 Jan 18, 2022
2 Nov 07, 2021
7 May 29, 2022
2 Dec 15, 2021
1 Dec 23, 2021
0 Mar 24, 2022
3 Jul 05, 2022
1 Oct 18, 2021
4 Sep 12, 2021
4.1k Dec 30, 2022
4 Jan 21, 2022
2 Jun 16, 2022
2.9k Jan 07, 2023
10 Oct 29, 2022
1 Nov 14, 2021
31 Jan 01, 2023