We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
upstream-source
Currently, charms are publishing its OCI image revision (e.g.: https://github.com/canonical/mysql-k8s-operator/releases/tag/rev132), however to discover the source of that given revision, we need to check the specific commit's metadata.yaml.
To make it easier for support, can we also attach that information to the releases?
The text was updated successfully, but these errors were encountered:
https://warthogs.atlassian.net/browse/DPE-3923
Sorry, something went wrong.
Since it's in a standardized format, this seems like a good idea
As with #160, would like to see something for this maybe land in charmcraft or get standardized across VM and K8s charms instead of K8s only
No branches or pull requests
Currently, charms are publishing its OCI image revision (e.g.: https://github.com/canonical/mysql-k8s-operator/releases/tag/rev132), however to discover the source of that given revision, we need to check the specific commit's metadata.yaml.
To make it easier for support, can we also attach that information to the releases?
The text was updated successfully, but these errors were encountered: