fix: relax aws provider constraints#100
Open
leonardofreitass wants to merge 1 commit intotryretool:mainfrom
Open
fix: relax aws provider constraints#100leonardofreitass wants to merge 1 commit intotryretool:mainfrom
leonardofreitass wants to merge 1 commit intotryretool:mainfrom
Conversation
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
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.
Summary
Relax AWS provider version constraints from pessimistic (~>) to minimum (>=) in aws_ecs and aws_ecs_ec2 modules
Reasoning
Reusable modules should only constrain their minimum allowed provider version (e.g. >= 5.0) rather than using pessimistic locking (~> 5.0). This avoids known incompatibilities while giving module consumers the flexibility to upgrade to newer provider versions without needing to modify the module.
At the moment, we are unable to use this module while using the newer AWS Provider v6
Reference: https://developer.hashicorp.com/terraform/language/providers/requirements#best-practices-for-provider-versions