Make sure the OIDC provider is stored in both our supported regions #1254
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.
Describe your changes
While working on https://github.com/dfds/cloudplatform/issues/2409 I discovered that updating my database instances could find the OIDC information, because Terraform could not find the /managed/cluster/oidc-provider path in SSM Parameter Store. It turns out that this data is only stored in eu-central-1, and if yoru database instance is in our other supported region (eu-west-1) , Terraform can not find it.
The solution is to make sure that entry is created in SSM for both our regions. I tested this with my sandbox capability account.
Issue ticket number and link
https://github.com/dfds/cloudplatform/issues/2409
Checklist before requesting a review
test/integration
folder to apply my changes in QA. Read the guide on adding environment variables in QAIs it a new release?
release:(major|minor|patch)
, following semantic versioning in this guide ornorelease
if there is no changes to the Terraform code