Support Swarm templating for driver-opt
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
https://github.com/docker/cli/pull/62 introduced the capability to pass in driver-opt to services so that network driver specific options can be sent in per service. Swarm templating on this parameter would be very useful for a variety of scenarios that need to send task or service-specific information to a network driver.
A similar request was also requested by https://github.com/moby/moby/issues/33408.
@stevvooe has offered to help with guidance if there are any contributors that want to take this on.
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 docker/cli pull request #62 and the related moby/moby issue #33408, then trace how driver-opt is represented and passed through SwarmKit services. Done means Swarm templating can provide task- or service-specific values for this parameter and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100