Rename plugin terminology in jobs; "plugin" instead of "name"
Open
Nobody has claimed this yet.
enhancement
good first issue
v2_overhaul
- Dominant language
- Go
- Stars
- 20
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
After feedback from multiple parties, it's not clear that the "name" in steps, targets managers, etc has to match with a plugin name from codebase.
Should switch all "name" references to "plugin", like:
- `"TargetManagerName": "targetlist"` -> `"TargetManagerPlugin": "targetlist"`
- step `{"name": "exec"}` -> step `{"plugin": "exec"}`
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
Search the repository for TargetManagerName and step references using name, then identify the other target-manager and step terminology mentioned in the issue. Update the relevant references consistently so plugin identifies the codebase plugin, and verify that the old terminology is no longer used in those interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100