Skip to content

Releases: garden-io/garden-action

v2.0

11 Jun 12:49
80be6df
Compare
Choose a tag to compare

What's Changed

The Kubeconfig inputs turned out to confuse some of our users. Now you need to create your Kubeconfig before calling the Garden Action. When using AWS EKS your GitHub workflow could look like this:

  garden-ci:
    runs-on: ubuntu-latest
    steps:
      - name: AWS auth
        uses: aws-actions/configure-aws-credentials@v1.7.0
        with:
          aws-region: eu-central-1
          role-to-assume: ${{ secrets.AWS_ROLE_EKS_DEV }}
          role-session-name: GitHubActionsDev
          role-duration-seconds: 3600
      - name: AWS EKS Kubeconfig
        run: |
          # Add EKS cluster ${cluster_name} to ~/.kube/config
          # NOTE: The context name will be the EKS cluster ARN by default.
          # If your Garden configuration expects a different context name,
          # you can add override it using the `--alias` option.
          aws eks update-kubeconfig --name ${cluster_name} --region ${region}
      - uses: actions/checkout@v3.0.2
      - name: Run tests in ci environment with Garden
        uses: garden-io/garden-action@v2
        with:
          command: >
            test --env ci
            --var postgres-database=postgres
            --var postgres-password=${{ secrets.PG_PASSWORD }}
          garden-auth-token: ${{ secrets.GARDEN_AUTH_TOKEN }}

Note that we are not passing the kubeconfig input anymore, but update the kubectl configuration (~/.kube/config) using the command aws eks update-kubeconfig

Full Changelog: v1.2...v2.0

v1.2

10 Oct 11:21
c221d0e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.1...v1.2

v1.1

06 Mar 10:28
6e74037
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0...v1.1

v1.0

21 Feb 12:49
b5f5b0f
Compare
Choose a tag to compare

Initial release.

What's Changed

Full Changelog: https://github.com/garden-io/garden-action/commits/v1.0