Allow glob in include statement paths
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 5.8k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 55
Description
Description
To create a compose environment that allows for plugins/extensions, we would like to be able to say:
services:
# common services for this designed environment
include: docker-compose.d/*.yml # admin selected plugins for this environment, loaded in alphabetical order
Of course, because the order of inclusion may matter for certain compose environments (not all), the glob would be sorted, and admins would have the ability to name their drop-in files as is customary in traditional unix subsystems that support drop-ins (e.g. /etc/sysctl.d, /etc/grub.d, /etc/X11/xinit/xinitrc.d, etc) : 00-firstcompose.yml, 05-earlycompose.yml, 99-finalcompose.yml, etc.
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 how Compose parses and resolves include statement paths, then find any existing include-related tests. Check how wildcard matches should be expanded and ordered, and define completion as supporting the requested glob form while preserving existing include behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, go
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100