Charmhub Integrations tab minor issues: wrong help/channel and missing charms
Closed this issue · 4 comments
Hi,
Several minor issues for the tab "Integrations" on charmhub.io:
- The bubble help says "Relation | Interface". IMHO, the correct is "Endpoint | Interface".
- Strange channel
8.0/stable/8.0
or14/stable/14
shown for charms where default track is not latest (e.g. mysql, postgresql). Example: https://charmhub.io/s3-integrator/integrations NOTE: the syntax14/stable/14
is reserved for<track>/<risk>/<branch>
(see "Anatomy of a channel" here). - For some reason here https://charmhub.io/mysql/integrations "No charms found that provide or consume s3", hovewer here https://charmhub.io/s3-integrator/integrations you can see four "Charms that consume s3". Can it be related to non-default/closed track
latest
?
Thank you for the answers and fixes!
Thanks for the report, Alex!
- The terminology was agreed some time ago, and I think it will probably need to be part of a larger discussion. Perhaps something @massigori might want to get involved with down the line. I'd like to avoid changing things without full agreement 🙂 .
- This is indeed a bug, that I'm fixing now 👍
- I think this is also a bug – I believe it is indeed the case that there are consumers of s3, but nothing in “latest” that provide. The issue is that the wording of the error is misleading, it should say “No charms found that provide s3” in this case. I'll also fix this 🙂
Dear @Lukewh , thank you for your comments and fixes!
I confirm the fix for issue #2 and wording improvements for #3. Tnx!
re: 3) .. but nothing in “latest” that provide 's3'.
There is a charm s3-integrator which is available in the latest/stable
and it provides s3
.
Q: why is it still missing in https://charmhub.io/mysql/integrations (section "s3")?
re: 1) "Relation | Interface" VS "Endpoint | Interface". CC: @simskij @jnsgruk
@taurus-forever it looks like “s3-integrator” is set as “unlisted”. This means that the charm is visible if you visit the URL directly, but it is not included in search results (which is how we populate the available integrations) :).