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
In Terraform configuration, it is recommended to define objects in alphabetical order of their name arguments, so that you get consistent and readable diff. Whenever objects are added or removed, or name is renamed, you'll observe a change in the majority of tasks. It's related to the fact that the current version of the provider treats object blocks as an ordered list. Alternatively, object block could have been an unordered set, though end-users would see the entire block replaced upon a change in single property of the task.
Hello, it seems Terraform doesn't support adding new tables to an existing delta share, please the diff and stack trace below:
And we are following the suggestion from https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/share#example-usage to sort objects alphabetically
Configuration
We first deployed
Then we added a few more tables then it looks like
Expected Behavior
Users should be able to add new tables if needed.
Actual Behavior
I assume it treats
main.schema_name.c
as a new table then tried to add it but it find it is duplicated with the existing one.Steps to Reproduce
1.41.0
Is it a regression?
Probably no.
Debug Output
Please check the ticket
Important Factoids
This is also tracked internally at https://databricks.atlassian.net/browse/ES-1110321. You can see more debugging logs there
Would you like to implement a fix?
The text was updated successfully, but these errors were encountered: