This PR adds a new option, --secrets-env-file, which works in essentially the same way as --env-file but adds the key/value pairs from this file into the secrets in the task definition instead of the environment.
The goal here is to allow users to use files like the below:
This PR adds a new option,
--secrets-env-file
, which works in essentially the same way as--env-file
but adds the key/value pairs from this file into the secrets in the task definition instead of the environment.The goal here is to allow users to use files like the below:
which will result in secrets being added to the task definition in the format:
This means, alongside a
.env
file, a single deploy can contain all the secrets and environment variables needed to configure an application correctly.