You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Devops admin, I'd like to deploy via docker-compose using environment variables for secrets, to automate deployments with secrets.
β Goals
Replace secrets in the generated compose file with environment variables
Provide an optional export of the environment variables and their generated values
π§° Possible Solution
Secrets in docker-compose files should be replaced with environment variables. e.g. ${SERVICE_PASSWORD_RABBITMQ}
A command line option to generate a .env file containing the secrets as environment variables should be available
The format of the environment variable names should be customisable around the service name. e.g. ${<ENV_PREFIX>_[SERVICENAME]_<ENV_SUFFIX>} where [SERVICENAME] is the name given to the service and the prefix/sufix are added either from config in Aspire or from command line arguments in Aspirate.
π Feature Description
As a Devops admin, I'd like to deploy via docker-compose using environment variables for secrets, to automate deployments with secrets.
β Goals
π§° Possible Solution
${SERVICE_PASSWORD_RABBITMQ}
${<ENV_PREFIX>_[SERVICENAME]_<ENV_SUFFIX>}
where[SERVICENAME]
is the name given to the service and the prefix/sufix are added either from config in Aspire or from command line arguments in Aspirate.For example...
π§ Blocked by
The text was updated successfully, but these errors were encountered: