In order to promote the charm on track 2 from edge to beta, beta to candidate, and candidate to stable, we can't rely on the current local promote workflows which eventually call the central one stored in this repo. This is because the local manually dispatched WF's don't accept a track input. So the central promote job is triggered with the default track of stable, which means we can't promote track 2 for example. To make the manually dispatched WF work for BE K8s, I added the track input. Should other charms implement a similar option?
The PR that implemented this change for BE K8s (with some more context) is: canonical/blackbox-exporter-k8s-operator#81
An example of a successful run is: https://github.com/canonical/blackbox-exporter-k8s-operator/actions/runs/22196059295
In order to promote the charm on track 2 from edge to beta, beta to candidate, and candidate to stable, we can't rely on the current local promote workflows which eventually call the central one stored in this repo. This is because the local manually dispatched WF's don't accept a track input. So the central promote job is triggered with the default track of stable, which means we can't promote track 2 for example. To make the manually dispatched WF work for BE K8s, I added the
trackinput. Should other charms implement a similar option?The PR that implemented this change for BE K8s (with some more context) is: canonical/blackbox-exporter-k8s-operator#81
An example of a successful run is: https://github.com/canonical/blackbox-exporter-k8s-operator/actions/runs/22196059295