publishergw: provide the revision to resource revision mappings created with `release` for charms

Bug #2081470 reported by Alex Lowe
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Snap Store Server
Expired
Wishlist
Unassigned

Bug Description

The release endpoint for charms allows mapping resource revisions to specific revisions, but we don't have a way to retrieve that data afterwards.

Ideally, list_resource_revisions would provide an array of workload revisions the resource revision maps to, and list_revisions would provide the resource revisions attached to that workload revision.

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Hello,

The mapping is actually the channel/release, the charm revision is not tied to the resource revision (or viceversa) in any way.
Could you elaborate a bit more on what are you trying to solve with this information?
The closest thing I can think of could be a channel-map history for the charm, showing all the releases for a specific channel (which include charm and resource revision)

Cheers

Changed in snapstore-server:
status: New → Incomplete
importance: Undecided → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Snap Store Server because there has been no activity for 60 days.]

Changed in snapstore-server:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.