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/[email protected]
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/[email protected]
- 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
Contributors
stefreak and twelvemo