Skip to content

enable_affected_projects_deployments produced an unexpected error after upgrading to 2.15 #296

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.

Sign up for GitHub

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

Jump to bottom
Open
tom-sherman opened this issue Apr 1, 2025 · 1 comment
Open

enable_affected_projects_deployments produced an unexpected error after upgrading to 2.15 #296

tom-sherman opened this issue Apr 1, 2025 · 1 comment

Comments

@tom-sherman
Copy link 

resource_name: Modifying... [id=prj_xxx]

Error: Provider produced inconsistent result after apply

When applying changes to
resource_name, provider
"provider[\"registry.terraform.io/vercel/vercel\"]" produced an unexpected
new value: .enable_affected_projects_deployments: was null, but now
cty.False.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.
@tom-sherman tom-sherman changed the title enable_affected_projects_deployments produced an unexpected after upgrading to 2.15 enable_affected_projects_deployments produced an unexpected error after upgrading to 2.15 Apr 2, 2025
@tom-sherman
Copy link
Author

My workaround was to apply an explicit enable_affected_projects_deployments = false to the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tom-sherman