Automate cluster-aws test pull requests

[nprokopic]

What does this PR do?

This PR adds a GitHub workflow that automates creation of test PRs in cluster-aws in order to test cluster chart changes.

The workflow gets triggered for every cluster chart pull request. It has 2 jobs:

1. one to create/update test PRs in cluster-aws
2. one to close cluster-aws PRs when cluster chart PRs are closed/merged.

The job that creates/updates cluster-aws PRs will do the following (simplified steps):

• Clone cluster-aws repo.
• Create a new cluster-aws branch called test-cluster-chart-pr-{{ cluster chart PR number }}. If the branch already existed it just checks out that branch.
• Update cluster chart version in test-cluster-chart-pr-{{ cluster chart PR number }} branch by setting it to a cluster chart version from the tested cluster chart PR.
• Open/update cluster-aws draft PR. See example PR here Test cluster chart PR #264 cluster-aws#689.

When cluster chart PR is closed, cluster-aws PR is closed as well.

What is the effect of this change to users?

Giant Swarm engineers can easily test provider-independent changes for CAPA.

Any background context you can provide?

CAPA is already GA, CAPZ will be GA soon, and all other providers will also soon start to use cluster chart, so without automated cross-provider testing the risk of issues slipping through cracks due to changes not being tested is very high.

Should this change be mentioned in the release notes?

No. This is CI change, no need to be included in the release notes.

[nprokopic]

/run cluster-test-suites

Let's try this 🙈

[nprokopic]

/run cluster-test-suites

[nprokopic]

/run cluster-test-suites

[nprokopic]

/run cluster-test-suites

[nprokopic]

/run cluster-test-suites

[nprokopic]

Closing to test of cluster-aws PR gets closed.

[github-actions]

There were no differences in the rendered Helm template.

Output

=== Differences when rendered with values file helm/cluster/ci/test-required-values.yaml ===

No difference


=== No differences at all ===

[taylorbot]

Test pull request has been created in cluster-aws repo. Go to pull request giantswarm/cluster-aws#690 to test you cluster chart changes on AWS.

[github-actions]

There were no differences in the rendered Helm template.

Output

=== Differences when rendered with values file helm/cluster/ci/test-required-values.yaml ===

No difference


=== No differences at all ===

[taylorbot]

Hey @nprokopic, a test pull request has been created for you in cluster-aws repo! Go to pull request giantswarm/cluster-aws#691 in order to test you cluster chart changes on AWS.

[nprokopic]

Works nicely! 🎉 Will merge this to try it out for cluster chart PRs with actual cluster chart changes. We can then improve this and do the same for other providers (like CAPZ).