docker / docker/cli

Followup to #1564 (cli plugins)

Open
#1,661 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/plugins kind/enhancement
Dominant language
Go
Stars
6.1k
Forks
2.2k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

From #1564 (comment):

Others:

  • plugins shuld be able to indicate if they are "management" vs not commands in their metadata and be listed accordingly in e.g. docker help → See PR #1684.
  • plugins should have a field in config.json for their use, see Configuration in design → See PR #1652.
  • plugins should call back to main cli using dial-stdio to connect to engine. From https://github.com/docker/cli/issues/1534#issuecomment-446206041 → See PR #1654 .

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the remaining unchecked items and the linked discussion from PR #1564, focusing on docker someplugin --version, docker-myplugin --version, and the sample plugin's usage output. Done means deciding and implementing the plugin version API and correcting the sample plugin output, while accounting for the related work already moved to issues and pull requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.