Tell us about your request
Just like it can be done on any CI solution (Github Actions, Bitbucket Pipelines, ...), it would be great if we could store at the Desktop client level some environment variable and secrets, which would be pass when the dev environment is created, especially, when building from a git remote repository.
Which service(s) is this request for?
Docker Desktop (for Windows or Mac)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I build Firebase projects, which require to be logged in to Firebase. During the build process, I need to pass an auth token in order to set the project in a certain state.
Are you currently working around the issue?
Yes, by using a local repository instead of creating the dev environments directly from the repo directly. However, I cannot share the image as it would require to store some credentials, and I do have to be careful not saving this credentials in some files that would be added to the repo.
Additional context
As this is not particulary easy to explain, I would essentially recommend that the UI for dev environment is allowing to 1) store the git repos for which I would create dev environments regularly, and 2) save for each of them environment variables and secrets which would be added to the docker-compose.yaml (and subsequent Dockerfile(s)). Secrets would have to be store in a way that would make it hard to figure them out should the computer be stolen (typically storing them on Keychain on Mac).
Tell us about your request Just like it can be done on any CI solution (Github Actions, Bitbucket Pipelines, ...), it would be great if we could store at the Desktop client level some environment variable and secrets, which would be pass when the dev environment is created, especially, when building from a git remote repository.
Which service(s) is this request for? Docker Desktop (for Windows or Mac)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I build Firebase projects, which require to be logged in to Firebase. During the build process, I need to pass an auth token in order to set the project in a certain state.
Are you currently working around the issue? Yes, by using a local repository instead of creating the dev environments directly from the repo directly. However, I cannot share the image as it would require to store some credentials, and I do have to be careful not saving this credentials in some files that would be added to the repo.
Additional context As this is not particulary easy to explain, I would essentially recommend that the UI for dev environment is allowing to 1) store the git repos for which I would create dev environments regularly, and 2) save for each of them environment variables and secrets which would be added to the docker-compose.yaml (and subsequent Dockerfile(s)). Secrets would have to be store in a way that would make it hard to figure them out should the computer be stolen (typically storing them on Keychain on Mac).
Many thanks in advance.