-
Notifications
You must be signed in to change notification settings - Fork 99
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
[TF-10414] Upgrade modules to AWS V5 provider #316
Conversation
/test all destroy=true ❌ Terraform AWS Public Active/Active (Legacy) - Test Report
✅ Terraform AWS Private Active/Active (FDO) - Test Report
✅ Terraform AWS Active/Active RHEL7 Proxy (FDO) - Test Report
❌ Terraform AWS Private TCP Active/Active (FDO) - Test Report
✅ Terraform AWS Public Active/Active (FDO) - Test Report
✅ Terraform AWS Private Active/Active (Legacy) - Test Report
❌ Terraform AWS Private TCP Active/Active (Legacy) - Test Report
✅ Terraform AWS Standalone Vault (FDO) - Test Report
✅ Terraform AWS Standalone Vault (Legacy) - Test Report
❌ Terraform AWS Active/Active RHEL7 Proxy (Legacy) - Test Report
|
/test public-active-active-replicated destroy=false ✅ Terraform AWS Public Active/Active (Legacy) - Test Report
|
/test private-tcp-active-active destroy=false ❌ Terraform AWS Private TCP Active/Active (FDO) - Test Report
❌ Terraform AWS Private TCP Active/Active (FDO) - Test Report
|
/test private-tcp-active-active-replicated destroy=false ❌ Terraform AWS Private TCP Active/Active (Legacy) - Test Report
|
/test active-active-rhel7-proxy-replicated destroy=false ❌ Terraform AWS Active/Active RHEL7 Proxy (Legacy) - Test Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failing tests appear to be the result of cloud resource errors and replicated.com
needing to be added to the no_proxy
list, not due to any changes in this PR. A follow up PR will be made to address the failures.
/destroy active-active-rhel7-proxy-replicated ✅ Terraform AWS Active/Active RHEL7 Proxy (Replicated) - Destruction Report
|
/destroy private-tcp-active-active-replicated ✅ Terraform AWS Private TCP Active/Active (Replicated) - Destruction Report
|
/destroy private-tcp-active-active ✅ Terraform AWS Private TCP Active/Active (FDO) - Destruction Report
|
/destroy public-active-active-replicated ✅ Terraform AWS Public Active/Active (Replicated) - Destruction Report
|
Background
Some of the AWS APIs supported in V4 are going to get deprecated by EOY. Not to mention that some flaky situations have been spotted during the execution of modules relying on V4, which have been addressed on V5.
This PR upgrades the version constraints of the modules to rely on the AWS V5 provider.
Relates OR Closes #0000
How Has This Been Tested
I ran
terraform init
in each submodule to verify this is not introducing breaking syntax.