Closed savroman closed 2 years ago
I was able to reproduce.
In fact the default value of the capacity_reservation_specification should remain null instead of {}
@bryantbiggs : I can revert this back to what it was originally
let me take a deeper look locally
ran into the same error today and confirmed @savroman's note with downgrading to 4.1.2 worked for me as well.
looks like the module testing should be improved.
looks like the module testing should be improved.
sponsorships are always welcomed so we can dedicate more time
This issue has been resolved in version 4.1.4 :tada:
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.
Description
Running terraform plan cased the issue
If your request is for a new feature, please use the
Feature request
template.β οΈ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Done! But not helps.
Versions
Reproduction Code [Required]
Steps to reproduce the behavior: terraform init terraform plan
Expected behavior
plan output
Actual behavior
Terminal Output Screenshot(s)
Additional context
Downgrade to 4.1.2 fixes the issue