a way to know what plugins work in which version of pulp-cli.

[fkuep]

Excuse

Thanks for all the work!
I am very blunt here and I hope You can take it as my despair.

reference

#394 , pulp/pulpproject.org#361

Summary

As a user I don't know what plugins exsist and if they work together.
I don't know if there is a much cleverer way, but I will just start to suggest:

• You take issues for plugin-writers to "register" their pypi links.
  Then You could:
  • have a ci script install those into a current version pulp-cli
  • execute some sort of "list-commands"
  • Make the Known plugins table, a "known to work with this version of pulp-cli "-table.

My Problem as user, right now :
*I am not even convinced I don't end up with multiple venvs of cli to support Your release process. Not something I intend to deal with as a user. *

[mdellweg]

I'm not sure what plugins you are talking about. The cli itself has only one known plugin (pulp-cli-deb) which is not ready for consumption.
If you are talking about compatibility with pulp plugins, the cli is compatible with at least 5 pulpcore releases in a row. That means current 0.12.0 is compatible with 3.11 to 3.16 and the corresponding plugin versions.

[fkuep]

I am generally talking about You publishing Your tested featureset in a prominent place.

@mdellweg
You approved commit pulp/pulpproject.org@00e6a44
while the tests in tests/scripts knew about signing-service and migration.
Could You generate a docs/suported_workflows.md file that e.g. starts with tested against pulp 3.16 and lists e.g:
pulp_file:

• Sync
• upload
  ?

@daviddavis
You did the last Release, is it easy to add docs/CHANGES.md (or the fragment of that version)
to the next Releases ?
That could be an improvement by itsself, plus as long as pulpproject announces pulp-cli's features they have a way to it lookup in an authoritative place.