Ability to watch for dependent service rebuilds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 5.8k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 55
Description
Description
I have a Compose file that builds multiple services, one of which ends up being an additional context for the other. Like this:
services:
service1:
build: ./components/service1
service2:
build: ./components/service2
additional_contexts:
service1: service:service1
While I can add Compose Watch config to service1 and have it rebuild, there's no mechanism available to trigger a rebuild of service2.
Therefore, it would be nice to have a mechanism that would allow me to rebuild/restart service2 when a rebuild of service1 has occurred.
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 by tracing Compose Watch handling and how additional_contexts are represented in the service dependency graph. Define the rebuild and restart behavior for a dependent service, including how completion of the watched service rebuild triggers it; the issue provides no file or test entry point, so the relevant implementation and validation coverage must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100