Closed joernheissler closed 6 years ago
FYI there's already a PR associated with this: #4367
The simple fix of removing the v != 0
check has been merged into master via #4367 and will release with v1.19.0 of the AWS provider, likely middle of next week. If there are other continuing issues after that, please open a new issue. Thanks!
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Community Note
Terraform Version
Affected Resource(s)
aws_launch_template
Terraform Configuration Files
Expected Behavior
Terraform should submit the device index (0) to AWS.
Actual Behavior
Terraform ignores zero device index. AWS will then complain:
You must use a valid fully formed launch template. Each network interface requires a device index.
Steps to Reproduce
Important Factoids
By deleting the default VPC, AWS will complain
No default VPC for this user
. So I specifiednetwork_interfaces
like above and got the problem described above.I quick fixed the issue in
aws/resource_aws_launch_template.go
:I removed
&& v != 0
and when I first destroyed the resource, it got created correctly on next apply. But updates don't work, probably another comparison that needs fixing.