Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle multiple platforms for channel map in status #129

Closed
matiasb opened this issue Aug 19, 2020 · 1 comment · Fixed by #403
Closed

Handle multiple platforms for channel map in status #129

matiasb opened this issue Aug 19, 2020 · 1 comment · Fixed by #403
Labels
store Related to the interaction with the Store
Milestone

Comments

@matiasb
Copy link

matiasb commented Aug 19, 2020

If a charm support multiple series (platforms), there could be different released revisions for each of them (eg. revision 1 released to (stable, xenial) and revision 2 to (stable, focal)). FWIW, this is similar for snaps, snapcraft and multiple architectures

charmcraft is currently rendering one released value for each channel, ignoring the platform.

@facundobatista facundobatista added the store Related to the interaction with the Store label Aug 31, 2020
@facundobatista facundobatista added this to the soon milestone Oct 14, 2020
@maxiberta
Copy link

Note that charm "platforms" is being superseded by "bases". Support for platforms (unused at the moment) is being dropped from Charmhub (/v1/<namespace>/<name>/revisions and /v1/<namespace>/<name>/releases). Eventually, bases will need to be exposed for a complete status output.

@facundobatista facundobatista modified the milestones: soon, 1.1 Jun 7, 2021
facundobatista added a commit to facundobatista/charmcraft that referenced this issue Jun 23, 2021
Note about some `all_tracks`-related code deletion: we're now Python 3.6+, so we can rely on dict's order.

Fixes canonical#129.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
store Related to the interaction with the Store
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants