Closed NickHirras closed 2 years ago
Thanks for raising this, @NickHirras. The provider hasn't supported CloudHSM v1 in several years, but the documentation was not correctly updated.
This functionality has been released in v4.2.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
terraform cli v1.1.5 on Debian buster
hashicorp/aws v4.0.0
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Expected Behavior
Terraform configured to use localstack endpoints for all services
Actual Behavior
Steps to Reproduce
terraform plan
Important Factoids
Running against localstack, although not sure that's impacting this step.
References
This is listed as a valid configuration key in terraform docs. See: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/custom-service-endpoints#cloudhsmv1