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 databricks_recipient resource #4392

Open
cjf-fuller opened this issue Jan 10, 2025 · 0 comments
Open

[ISSUE] Issue with databricks_recipient resource #4392

cjf-fuller opened this issue Jan 10, 2025 · 0 comments

Comments

@cjf-fuller
Copy link

Configuration

resource "databricks_recipient" "recipient" {
  provider = databricks.workspace

  name                               = var.recipient_name
  authentication_type                = "DATABRICKS"
  
  data_recipient_global_metastore_id = var.recipient_metastore_id
}

Expected Behavior

A databricks_recipient object is created in the source Databricks workspace that is linked to the provider = databricks.workspace

A databricks provider object is created in the recipient Databricks workspace

At some time later the databricks provider object is removed from the recipient Databricks workspace.

I would expect it to be recreated by a subsequent run in the source Databricks workspace (as that is where it was initially created, and tracked in state here)

Actual Behavior

The databricks provider object is not recreated. It is only recreated if the databricks_recipient object is removed and recreated.

Steps to Reproduce

Deploy

resource "databricks_recipient" "recipient" {
  provider = databricks.workspace

  name                               = var.recipient_name
  authentication_type                = "DATABRICKS"
  
  data_recipient_global_metastore_id = var.recipient_metastore_id
}

Remove the created Provider object. Rerun terraform.

Terraform and provider versions

source  = "databricks/databricks"
version = "1.41.0"

Would you like to implement a fix?

Happy to help if I can, I wonder if the fix would be either to track the provider object as its own TF object, or attempt to monitor for the existence of the provider object when the source Databricks workspace is refreshed.

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