Repository navigation
Conversation
avnes
suggested changes
Aug 6, 2026
| description: 'DNS zone passed to the integration tests as INTEGRATION_DNS_ZONE.' | ||
| required: true | ||
| type: string | ||
| integration-atlantis-deploy: |
Contributor
There was a problem hiding this comment.
I think we should rather enable Atlantis in standby cluster. Hence this variable becomes not relevant.
Contributor
Author
There was a problem hiding this comment.
I agree, but since it will require infra change, I'd rather it not be a blocker for this change. I can create a separate task for this change. Sound fine?
Contributor
There was a problem hiding this comment.
It's fine if you remove his boolean first.
|
Closed after discussion with Mikkel over slack |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new reusable workflow for provisioning EKS clusters and running integration tests, along with an example of how to consume this workflow. The workflow consolidates environment-specific pipelines into a single, parameterized pipeline and leverages GitHub Actions' reusable workflow features.
Reusable workflow for EKS provisioning and integration testing:
.github/workflows/automation-eks-provision-and-integration-test.yml, which provisions an EKS cluster using Terragrunt, waits for resources to be ready, and runs integration tests using a built test binary. The workflow is highly configurable via inputs and secrets, supporting different environments and test configurations.Example usage:
examples/automation-eks-provision-and-integration-test.ymlto demonstrate how to use the reusable workflow. This example shows how to pass required parameters and secrets, and describes the workflow's purpose and usage.