Plugin lifecycle

[mloiseleur]

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:

1. plugin-service fails to download (valid) plugin with the old naming. For instance, tommoulard/fail2ban plugin is still valid up to v6.0.2. You can check it here.
2. The change is not visible in plugin-catalog UI
3. 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.

[ldez]

The problem with the repo of tom is known, it's not an issue with our service but with the user.

The plugin service doesn't work as GitHub but as a Go proxy: the module names are case sensitive due to several reasons related to Go.

[ldez]

The problem behind the names has been fixed in the service, only the tom's repo is still a problem for historical reasons.

[ldez]

Also, the problem is not related to the repo name but to the module name and plugin name.

https://github.com/traefik/plugindemo/blob/173560df05cb3e43cefc7dd4b592eef74188a19b/.traefik.yml#L5

[mloiseleur]

Also, the problem is not related to the repo name but to the module name and plugin name.

https://github.com/traefik/plugindemo/blob/173560df05cb3e43cefc7dd4b592eef74188a19b/.traefik.yml#L5

Yes, thanks. I updated the issue accordingly.