You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading to provider version 0.30.0, running terraform plan may produce some unexpected errors on certain attributes that belong to resources migrated to Framework, as outlined in 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.
Environment and versions:
Terraform Version: 0.12.4
Octopus Terraform Provider Version: 0.30.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
After upgrading to provider version
0.30.0
, runningterraform plan
may produce some unexpected errors on certain attributes that belong to resources migrated to Framework, as outlined in 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.
Environment and versions:
0.12.4
0.30.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: