Skip to content

[ISSUE] Issue with databricks_mws_ncc_private_endpoint_rule resource #4559

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

Open
marvinbuss opened this issue Mar 6, 2025 · 2 comments
Open

Comments

@marvinbuss
Copy link

Configuration

resource "databricks_mws_ncc_private_endpoint_rule" "ncc_private_endpoint_rule" {
  provider = databricks.account

  for_each = var.databricks_private_endpoint_rules

  network_connectivity_config_id = data.databricks_mws_network_connectivity_config.network_connectivity_config.network_connectivity_config_id

  resource_id = each.value.resource_id
  group_id    = each.value.group_id
}

Expected Behavior

Private Endpoints being created successfully.

Actual Behavior

Error is thrown on every apply.
│ Error: cannot create mws ncc private endpoint rule: The service at /api/2.0/accounts//network-connectivity-configs//private-endpoint-rules is taking too long to process your request. Please try again later or try a faster operation. [TraceId: ]

Steps to Reproduce

Terraform and provider versions

  1. Create the Databricks Config shown above
  2. Use a for_each with ~ 10 items.
  3. Terraform apply

Is it a regression?

I think it has gotten worse over the last few weeks.

Debug Output

I can share that if necessary. But I don't think this is crucial right now since this is related to the API itself.

Important Factoids

No

Would you like to implement a fix?

@sebastianczech
Copy link

I have the same problem as described in #4138 .

@sebastianczech
Copy link

I've tested new provider 1.74.0 and behaviour is still the same.

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

2 participants