You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform Init Plan & Apply should be successful. ( Installation of latest provider hashicorp/aws "~> 5.0" should be successful.)
Actual Behavior
Terraform init failed with error added in description.
Steps to Reproduce
set up terraform provider configuration as mention in Terraform Configuration
terraform init
How much impact is this issue causing?
High
Logs
No response
Additional Information
There is new version of Terraform aws Provider released 4 hrs back causing pipeline failure, due to incorrect checksum. This is not happening in local run.
Looks like it's the issue for some platforms, Hashicorp released new version when this issue occurred last time.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Terraform CLI and Provider Versions
https://www.terraform.io/docs/cli/plugins/signing.html
│ Error: Failed to install provider
│
│ Error while installing hashicorp/aws v5.71.0: archive has incorrect
│ checksum
│ zh:21f5d77f2859d9ddb5fafa7b6cfd0efdf82977c631ce788e56728afc6da17323
│ (expected
│ zh:c164d3ed13eb4c28ac243221591fc4ac3cfe621f8cd20af533dedd98a6387363)
╵
Error: Process completed with exit code 1.
Terraform Configuration
Expected Behavior
Terraform Init Plan & Apply should be successful. ( Installation of latest provider hashicorp/aws "~> 5.0" should be successful.)
Actual Behavior
Terraform init failed with error added in description.
Steps to Reproduce
set up terraform provider configuration as mention in Terraform Configuration
terraform init
How much impact is this issue causing?
High
Logs
No response
Additional Information
There is new version of Terraform aws Provider released 4 hrs back causing pipeline failure, due to incorrect checksum. This is not happening in local run.
Looks like it's the issue for some platforms, Hashicorp released new version when this issue occurred last time.
Code of Conduct
The text was updated successfully, but these errors were encountered: