Open taurus-forever opened 1 year ago
Just for the history:
STR: open the Integration page and switch channels.
Actual result: it always shows information for charmhub default track / stable risk
(14/stable for example above).
Expected results: The Integration page must respect the chosen channel (latest/stable, 14/stable, 14/candidate, 14/beta, 14/edge).
Tnx!
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/WD-11698.
This message was autogenerated
Fixed! Try on https://charmhub.io/mongodb/integrations
The fix confirmed. You have made Charmhub.io great again! THANK YOU!!!
P.S. charms to play with:
https://charmhub.io/postgresql/integrations (tracks latest and 14 are completely different, nice to test filters here)
https://charmhub.io/mysql/integrations (has new integration tracing
for 8.0/edge risk)
https://charmhub.io/pgbouncer/integrations (tracks latest
and 1
are complete different)
https://charmhub.io/grafana-agent (also shows properly results on the filter)
NICE! All correct, no issues spotted. Well done!
Credit to @abbiesims
Hi,
It looks like channels are completely ignored (track
stable
always used) onIntegrations
tab of the charmhub.io E.g. Mongodb does support TLS indpe/edge
and5/edge
, but charmhub.io does not show interfacetls-certificates
when I am in context of those branches.Is it possible to fix/improve it? E.g. if I am watching
5/edge
track in my charm => shows5/edge
interfaces, e.g.tls-certificates
. At they are different tolatest/stable
. BTW,5/stable
andlatest/stable
are often different.Tnx!