[Proposal] Configuration for resources/operations other than stacks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Currently the Compose file and docker stack is the only way to define operations in a configuration file. This config allows users to perform stack operations, and create networks, but not much else.
There have been a few requests for a config format which is more build/dev/test oriented, for performing developer tasks, or adhoc operations. A config and command to support these sequential (not service) worksflows would be a great addition.
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 reviewing the Docker CLI's existing Compose-file and docker stack operation handling. The issue describes a new configuration format and command for sequential, non-service workflows; done would mean that the supported scope and behavior are defined and implemented, with appropriate validation and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100