Skip to content

Conversation

@jrobison-sb
Copy link
Contributor

Summary

We would like to be able to upgrade to AWS provider v5.0, which was just recently released.

How did you test this change?

Clone this repo locally, change the version pin, then change my source for the module to point at my local copy. Then I ran a terraform plan and verified that it works, with no diffs.

Issue

#45

@jrobison-sb
Copy link
Contributor Author

I also noticed that CI is still being tested using provider version 3. I'm happy to copy/paste a new test case which uses provider v5, or just bump the existing test cases to use v5.

@dmurray-lacework
Copy link
Collaborator

make it so

@jrobison-sb
Copy link
Contributor Author

@dmurray-lacework thanks for reviewing this. Since CI passed, could we get this merged (and then also get a new release)? Thanks.

versions.tf Outdated

required_providers {
aws = ">= 3.0, < 5.0.0"
aws = ">= 3.0, < 6.0.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jrobison-sb from discussion on the other module PR's we'd like to follow the approach here to versioning lacework/terraform-aws-config#65

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dmurray-lacework I pushed a new commit which pins >= 3.0. Thanks.

@dmurray-lacework
Copy link
Collaborator

make it so (run tests)

@dmurray-lacework dmurray-lacework changed the title [DEV-2665] support AWS provider v5 feat: add support for AWS provider v5 Jun 2, 2023
@dmurray-lacework dmurray-lacework merged commit 6a5c4f3 into lacework:main Jun 2, 2023
@lacework-releng lacework-releng mentioned this pull request Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants