canonical / canonical/data-platform-workflows
[RFE] Include SNAP revision that was used at given charm release
- Dominant language
- Python
- Stars
- 8
- Forks
- 17
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
Can we extend the text in, for example: https://github.com/canonical/mysql-operator/releases/tag/rev220
To also contain the snap revision that was used for a given deployment. This way a given user, e.g. support teams, can quickly relate charm <> snap. I believe we can pull that information at the end of integration testing.
We should also should check if the snap is set as "held".
Contributor guide
Research direction
Inspect the rev220 release page and the repository's integration-testing workflow first, since the issue suggests collecting this information there. Done means the release text records the SNAP revision associated with the charm release and indicates whether the SNAP is held.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100