Stack Deployment: Generate env files from secret vaults (Vault / Infisical) #11297
radhakrisri
started this conversation in
Ideas
Replies: 1 comment
-
|
Any updates on this since 2024? I'm planning to work on it myself in a local branch. Anyone interested in doing it with me? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe
Bringing up applications like authentik (https://docs.goauthentik.io/docs/installation/docker-compose), plane.so (https://docs.plane.so/docker-compose) etc... involves the following process:
This process is applicable to a significant number of applications, not just both above.
Managing these modified .env files for a number of services usually involves version controlling them in git. More flexible schemes involve managing them in secret vaults like Hashicorp Vault or Infisical.
Typically these secret vault solutions provide mechanisms to export the secrets into a .env format.
However, one needs to stitch up a different workflow/ script to generate these .env files and then deploy the docker-compose.yml as a stack in portainer.
Describe the solution you'd like
A solution like this streamlines the entire deployment process and provides a much more automated and robust mechanism:
This provides a streamlined workflow for deploying stacks in Portainer.
Describe alternatives you've considered
Alternatives I've been using is to maintain a script that talks to Portainer API and Infiscial API to orchestrate generate of .env and deploying stacks with portainer.
Additional context
None
Beta Was this translation helpful? Give feedback.
All reactions