From 8bd90bd2ff0bbb92c586c4e9755fa1f4319113b3 Mon Sep 17 00:00:00 2001 From: Jacques ROUSSEL Date: Mon, 23 Dec 2024 09:15:11 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=91=B7(helm)=20add=20a=20github=20workflo?= =?UTF-8?q?w=20to=20publish=20a=20chart?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We have a dedicated deployment repository, also containing the Helm chart. To avoid duplicating and maintaining twice a chart, we decided to publish our Helm chart. At first we tried the official chart releaser action, however, this ended in creating a new release on Github for each chart update, which wasn't acceptable. --- .github/workflows/release-helm-chart.yaml | 35 +++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 .github/workflows/release-helm-chart.yaml diff --git a/.github/workflows/release-helm-chart.yaml b/.github/workflows/release-helm-chart.yaml new file mode 100644 index 00000000..9ded4246 --- /dev/null +++ b/.github/workflows/release-helm-chart.yaml @@ -0,0 +1,35 @@ +name: Release Chart +run-name: Release Chart + +on: + push: + paths: + - src/helm/meet/** + +jobs: + release: + # depending on default permission settings for your org (contents being read-only or read-write for workloads), you will have to add permissions + # see: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token + permissions: + contents: write + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + with: + fetch-depth: 0 + + - name: Cleanup + run: rm -rf ./src/helm/extra + + - name: Install Helm + uses: azure/setup-helm@v4 + env: + GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}" + + - name: Publish Helm charts + uses: numerique-gouv/helm-gh-pages@add-overwrite-option + with: + charts_dir: ./src/helm + linting: off + token: ${{ secrets.GITHUB_TOKEN }}