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

[ISSUE] Issue with Catalog/Schema resource #3589

Open
satviksr-db opened this issue May 17, 2024 · 0 comments
Open

[ISSUE] Issue with Catalog/Schema resource #3589

satviksr-db opened this issue May 17, 2024 · 0 comments

Comments

@satviksr-db
Copy link

satviksr-db commented May 17, 2024

I was changing the name of a catalog, there was a schema that was using said catalog, it produced a plan where it wanted to change catalog name in place and replace schema as the catalog name has changed. However, it resulted in this error. I worked around error this by forcign the catalog also to be replaced instead of changing in place.


Error: Provider produced inconsistent final plan

When expanding the plan for databricks_schema.sentinel_schema to include new
values learned so far during apply, provider
"registry.terraform.io/-/databricks" produced an invalid new value for
.catalog_name: was cty.StringVal("sentinel-catalog-dcw"), but now
cty.StringVal("sentinel-catalog").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Configuration

# Copy-paste your Terraform configuration here

Expected Behavior

Actual Behavior

Steps to Reproduce

Terraform and provider versions

Is it a regression?

Debug Output

Important Factoids

Would you like to implement a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant