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

Terraform plan/apply fails if Azure Databricks Access Connector is manually deleted #19863

Closed
1 task done
nsenno-dbr opened this issue Jan 5, 2023 · 3 comments · Fixed by #19871
Closed
1 task done

Comments

@nsenno-dbr
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.0.1

AzureRM Provider Version

3.37.0

Affected Resource(s)/Data Source(s)

azurerm_databricks_access_connector

Terraform Configuration Files

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "=3.37.0"
    }
  }
}

provider "azurerm" {
  features {}
}


resource "azurerm_databricks_access_connector" "this" {
  name                = "nsenno-mi"
  resource_group_name = "nsenno"
  location            = "East US 2"

  identity {
    type = "SystemAssigned"
  }

  tags = {
    Owner = "nick.senno@databricks.com"
  }
}

Debug Output/Panic Output

https://gist.github.com/nsenno-dbr/9e041f081f801870ff61ede1971396ac

Expected Behaviour

After manually deleting the Azure Databricks Access Connector, running Terraform plan should gracefully determine that the connecter no longer exists and plan to create one.

Actual Behaviour

Terraform plan/apply results in an error. The error is a "ResourceNotFound" error. However, Terraform should be able to gracefully handle this scenario without erroring out of the plan state

Steps to Reproduce

  1. terraform apply
  2. manually delete the Azure Databricks Access connector using the Azure portal
  3. terraform plan

Important Factoids

n/a

References

No response

@myc2h6o
Copy link
Contributor

myc2h6o commented Jan 5, 2023

Hi @nebrass thanks for opening the issue! This is indeed a bug in the provider, I've opened #19871 to fix the issue.

@github-actions
Copy link

github-actions bot commented Jan 6, 2023

This functionality has been released in v3.38.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Feb 6, 2023

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants