Deploy Environment - Pulumi ESC Support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Currently we are able to add a list of environment variables to a Docker Compose deployment. I would like to be able to add support for Pulumi ESC by simply being able to prepend esc run [<org-name>/][<project-name>/]<environment-name> [flags] -- [command] before the docker compose command. https://www.pulumi.com/docs/esc/cli/commands/esc_run/
Describe the solution you'd like
Ideally during the server setup it would install Pulumi ESC. Then in the GUI you'd be able to set your Access Token which would also log you into the CLI. Once logged in you'd be able to simply set the [org-name]/[project-name]/[environment-name] you'd want to run before each deployment.
Describe alternatives you've considered
N/A - additional support could be added for others later
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the Docker Compose deployment flow, server setup, and GUI configuration for environment variables, then trace how deployment commands are assembled. Done would require a defined approach for installing and authenticating Pulumi ESC and selecting an environment before deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100