Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Maintenance ] Consider loosening AWS Provider pinning #158

Open
gwright99 opened this issue Nov 15, 2024 · 2 comments
Open

[ Maintenance ] Consider loosening AWS Provider pinning #158

gwright99 opened this issue Nov 15, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@gwright99
Copy link
Collaborator

gwright99 commented Nov 15, 2024

The current solution is tightly pinned to the 5.12.x version of the TF AWS Provider.

The current configuration version = "~> 5.12.0" means that the patch version can increment, but not the major or - more importantly - the minor version.

For ongoing maintenance efforts and acquisition of functionality in the 5.x.x series, it may be preferable to implement a different strategy like: version = ">= 5.12.0, < 6.0.0". This is both:

  1. Explicit (and generally more clear than the equivalent ~> shorthand).
  2. Provides an opportunity to easily grab new features/fixes via terraform init -upgrade.

There is a downside, however, in that some organizations' change control processes may not allow these looser pinning. Further investigation required.

@gwright99 gwright99 self-assigned this Nov 15, 2024
@gwright99 gwright99 added the question Further information is requested label Nov 15, 2024
@gwright99
Copy link
Collaborator Author

@schaluva -- any thoughts on the topic above?

@gwright99 gwright99 changed the title [ Maintenance ] Consider loosing AWS Provider pinning [ Maintenance ] Consider loosening AWS Provider pinning Nov 15, 2024
@schaluva
Copy link
Collaborator

Initial thought is to not loosen the constraint so as not to introduce another point of potential variability. There are already lots of knobs and levers that can be configured differently across users of the installer so I think if efforts of changing the pinned version are not too high, it feels safer to have the pinned version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants