Include name top-level element in cli compose schema
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
https://github.com/compose-spec/compose-spec/blob/master/spec.md#name-top-level-element
this should be available for use with e.g. docker stack deploy.
tbc: how to harmonize it with the existing arg (project name) -> preferred to make it optional and raise an exception when its passed to CLI & included in the compose file
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 with the Compose Specification's top-level name element linked in the issue, then trace how the Docker CLI handles the existing project-name argument and docker stack deploy. Define the behavior when both the CLI argument and compose-file name are supplied; done means the schema and deployment path consistently support the optional name without unresolved conflict handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100