Support array of env_file for docker_compose
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
Now we have the option to pass multiple --env-file for docker compose commands, so it'd be great if we could use it inside docker_compose's env_file parameter
Current Behavior
Now is just allowed to pass a single path containing the .env file
Why Do You Want This?
It's now a docker compose feature so we can replicate to Tilt
Additional info:
Issue already closed for docker compose: https://github.com/docker/compose/issues/7326
Feature's pull request: https://github.com/docker/compose/pull/10284
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
Start at the docker_compose resource's env_file handling and compare it with Docker Compose's multiple --env-file behavior. Done means accepting multiple env-file paths and confirming docker_compose uses them in order, with coverage in the relevant existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, go
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100