apm plugin init has no way to set the plugin name that apm init --plugin <name> accepted

Open Beginner friendly
#4,075 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli

Research direction

Read the apm plugin init command and the migration docs that mention the gap; the issue does not name their file paths. Check how the command currently accepts arguments and compare it with the old apm init --plugin <name> form. Done means apm plugin init accepts a plugin name and the migration documentation reflects the supported form.

Written by the indexing model from the issue text.

Description

enhancement

With apm init --plugin removed in 0.37 (#4073), apm plugin init has no equivalent for the positional name argument the old form accepted. Add a name option (or positional) so the migration is complete. Outside #4073's scope; the docs note the gap.

Dominant language
Python
Stars
4.4k
Forks
430
Avg merge
2d 5h
Merged PRs (30d)
240

Getting set up

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.

More from microsoft/apm

All issues in microsoft/apm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.