change to ignition config prompts change instead of destroy & add

[nwbt]

Terraform Version

Terraform v0.11.2

• provider.ignition v1.0.0
• provider.vsphere v1.3.2

Affected Resource(s)

• provider.ignition v1.0.0

Terraform Configuration Files

N/A

Debug Output

N/A

Panic Output

N/A

Expected Behavior

When using ignition and there's an ignition configuration change, it seems reasonable to expect terraform plan & terraform apply to do a destroy and add instead of change. This expectation is based on the way ignition provisions the operating system, once on first boot.

Actual Behavior

Changes to the ignition configuration after the initial terraform apply appear to update the ignition configurations but the changes never propagate to the OS (CoreOS) as this is not how ignition operates. This causes an apply to appear successful while in reality the operation does nothing functionally.

Steps to Reproduce

1. terraform apply
2. Make any valid ignition change
3. terraform apply

Important Factoids

N/A

References

https://coreos.com/ignition/docs/latest/

[seh]

Are you using the ignition_config data source's "rendered" attribute in your machine configuration?