Getting terraform.ResourceAttrDiff on 1/0 vs true/false when running terraform apply

[rgynn]

Hello

I'm running Terraform v0.6.14

Been rewriting my states for a POP in AWS.
The resources have all been created already, but I wanted to add more variables and couters to my state files.
All the resources parameters should be exactly the same, just defined proceduraly.

However, as i'm doing a terraform apply (with a refresh), it sets my attributes in the state files for booleans as strings, and apply apparently expects integers.

Running the same apply with -refresh=false, and manually setting every "true" / "false" to "1" or "0", runs fine.

For almost every single resource, i see the same error output from apply:

Old:"true", New:"1",

Diff One (usually from plan): *terraform.InstanceDiff{Attributes:map[string]*terraform.ResourceAttrDiff{"root_block_device.0.delete_on_termination":*terraform.ResourceAttrDiff{Old:"true", New:"1", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Type:0x0}, "associate_public_ip_address":*terraform.ResourceAttrDiff{Old:"true", New:"1", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Type:0x0}, "source_dest_check":*terraform.ResourceAttrDiff{Old:"true", New:"1", NewComputed:false, NewRemoved:false, NewExtra:interface {}(nil), RequiresNew:false, Type:0x0}}, Destroy:false, DestroyTainted:false}

Is there a way for me to get around this?

[robholland]

This is a duplicate of #6005 (same symptom and presumably underlying cause).

[phinze]

Consolidating with #6005 - see you there!

[ghost]

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.