traefik / traefik/plugin-service
Plugin lifecycle
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 9
- Avg merge
- 14d 17h
- Merged PRs (30d)
- 2
Description
Current Behavior
One can
a) change gh account name : from tommoulard to tomMoulard, for instance
b) move or fork the (same) plugin to another account: from my_repo to my_company, for instance
When it happens:
plugin-servicefails to download (valid) plugin with the old naming. For instance,tommoulard/fail2banplugin is still valid up tov6.0.2. You can check it here.- The change is not visible in plugin-catalog UI
- It generates tons of (false) error log.
Expected Behavior
When one rename his gh account, move or depreciate his plugin, this should be handled gracefully, on both backend & frontend sides. Both plugin developer or TraefikLabs should be able to handle this use case.
⚠️ GitHub accounts are case in-sensitive but Go Modules are case sensitive.
Contributor guide
No contributing guide indexed for this repository
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 tracing plugin-service's plugin download and error handling, then inspect the plugin-catalog UI path described in the issue. Determine how renamed, moved, or deprecated plugins are represented and how GitHub case sensitivity affects Go module names. Done means these cases are handled gracefully on both backend and frontend without false errors or stale catalog data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100