Richard
Results
2
comments of
Richard
Getting the same issue. This is occurring when upgrading the provider from `0.9.0` to `0.10.0` which appears to be caused by the addition of the `instance_configuration_version` field which previously did...
Workaround, inspecting the state after a failed apply shows that the value is set to 0; setting the `instsance_configuration_version` field to a value before an apply when upgrading the provider...