From 3b4a150de8eef168501ef12adfa924bf940d936e Mon Sep 17 00:00:00 2001 From: Daniela Plascencia Date: Mon, 17 Feb 2025 18:23:51 +0100 Subject: [PATCH] fix: use charmcraft promote in promote.yaml workflow (#677) This commit rewrites the promote.yaml workflow to use charmcraft promote command instead of the release-charm action.We can no longer use the release-charm action because it relies on having GH releases in the repo, which we have stopped producing since migrating our CI to data-platform-workflows Part of canonical/bundle-kubeflow#1202 --- .github/workflows/promote.yaml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/.github/workflows/promote.yaml b/.github/workflows/promote.yaml index 8a33b385..5f4c9986 100644 --- a/.github/workflows/promote.yaml +++ b/.github/workflows/promote.yaml @@ -18,15 +18,15 @@ jobs: promote-charm: name: Promote charm runs-on: ubuntu-20.04 + env: + CHARMCRAFT_AUTH: ${{ secrets.CHARMCRAFT_CREDENTIALS }} steps: - - uses: actions/checkout@v3 - - name: Release charm to channel - # TODO: use canonical/charming-actions/promote-charm? - uses: canonical/charming-actions/release-charm@2.6.2 - with: - credentials: ${{ secrets.CHARMCRAFT_CREDENTIALS }} - github-token: ${{ secrets.GITHUB_TOKEN }} - destination-channel: ${{ github.event.inputs.destination-channel }} - origin-channel: ${{ github.event.inputs.origin-channel }} - tag-prefix: ${{ github.event.inputs.charm-name }} - charm-path: charms/${{ github.event.inputs.charm-name}} + - name: Install charmcraft + run: | + sudo snap install charmcraft --classic --channel latest/stable + - name: Run charmcraft promote + run: | + charmcraft promote --name ${{ github.event.inputs.charm-name }} \ + --from-channel ${{ github.event.inputs.origin-channel }} \ + --to-channel ${{ github.event.inputs.destination-channel }} \ + --yes