Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: provider produced an unexpected new value #774

Open
benPearce1 opened this issue Sep 3, 2024 · 0 comments
Open

Error: provider produced an unexpected new value #774

benPearce1 opened this issue Sep 3, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@benPearce1
Copy link
Collaborator

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.

@colinbowern colinbowern added the kind/bug Something isn't working label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants