fix: Restrict AWS provider max version due to v6 provider breaking changes #3384
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.
Description
Adds a version constraint to the aws provider, since 6.0 introduced changes that currently breaks v20.37.0.
This is just a workaround to make it work
Motivation and Context
Currently it not possible to use this Module, as terraform automatically downloads the newly released 6.0.0 aws provider
fixes #3383
Breaking Changes
This should not introduce breaking changes
How Has This Been Tested?
As this a trivial change I have skipped those steps. I've tested my branch on one of our Testing Cluster setups and it didn't change any resources.
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request