Investigation: what happens when two projects have the same name?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Had a thought that I wanted to capture for investigation later so I'm making an issue.
What happens when INCLUDE_ALL_COMPOSE_PROJECTS=true and you have multiple projects with the same name?
I expect it will either error (acceptable) or it will potentially overwrite volumes or databases with the same naming scheme (unacceptable).
I want the behavior to be a graceful early exit with a descriptive error message sent to the configured notification provider.
Contributor guide
No contributing guide indexed for this repository
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 how INCLUDE_ALL_COMPOSE_PROJECTS=true is handled and how project names are used for volumes or databases. Then inspect the configured notification provider path. Done means duplicate project names are detected before backup work begins, a descriptive error is sent, and no resources are overwritten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100