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

[FEATURE] Add ability to import databricks_notification_destination #4275

Open
kishaningithub opened this issue Nov 28, 2024 · 2 comments · May be fixed by #4276
Open

[FEATURE] Add ability to import databricks_notification_destination #4275

kishaningithub opened this issue Nov 28, 2024 · 2 comments · May be fixed by #4276
Labels
feature New feature or request

Comments

@kishaningithub
Copy link

kishaningithub commented Nov 28, 2024

From the provider documentation, i see that there is no way to import databricks_notification_destination resource. I would be great if this feature can be added.

Use case

  • We have lot of notification destination resources created manually via databricks UI. We would like to import the same into terraform.
@kishaningithub kishaningithub added the feature New feature or request label Nov 28, 2024
@alexott
Copy link
Contributor

alexott commented Nov 28, 2024

it works just not documented... For example:

terraform import databricks_notification_destination.this "12f83d99-15f6-4ca4-a909-c596fc6bed80"

P.S. Almost all Databricks resources support import

@alexott
Copy link
Contributor

alexott commented Nov 28, 2024

btw, you can use terraform exporter to generate code for existing objects - it will also create import definitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
2 participants