From the release of 0.30.0, the implementations of a number of resources and datasources have been converted from SDKv2 to Framework. This has introduced some breaking changes and unexpected behaviour.
Setting the ID on a resource can cause validation failure
If you set the value of the id attribute on a resource, the plan will fail due to a change in validation for the migrated resources as outlined on the 0.30.0 release
Error: provider produced an unexpected new value
There might be some errors around mismatched strings in the plan vs the state. These will look like this:
"provider[\"registry.terraform.io/octopusdeploylabs/octopusdeploy\"]"
produced an unexpected new value: .template[2].help_text: was null, but now
cty.StringVal("").
The workaround to this is to set the value in the config to an empty string.
Report the resource name and the path of these errors in this issue.
These errors are occurring because the Framework implementation is very strict, while the SDKv2 implementation was lenient in enforcement of data consistency.
benPearce1
commented
2 months ago
From the release of
0.30.0, the implementations of a number of resources and datasources have been converted from SDKv2 to Framework. This has introduced some breaking changes and unexpected behaviour.Setting the ID on a resource can cause validation failure
If you set the value of the
idattribute on a resource, the plan will fail due to a change in validation for the migrated resources as outlined on the 0.30.0 releaseError: provider produced an unexpected new value
There might be some errors around mismatched strings in the plan vs the state. These will look like this: "provider[\"registry.terraform.io/octopusdeploylabs/octopusdeploy\"]" produced an unexpected new value: .template[2].help_text: was null, but now cty.StringVal("").
The workaround to this is to set the value in the config to an empty string. Report the resource name and the path of these errors in this issue.
These errors are occurring because the Framework implementation is very strict, while the SDKv2 implementation was lenient in enforcement of data consistency.