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

[FEAT] Support for SQL Alerts and Destination #1136

Closed
vadivelselvaraj opened this issue Feb 23, 2022 · 8 comments
Closed

[FEAT] Support for SQL Alerts and Destination #1136

vadivelselvaraj opened this issue Feb 23, 2022 · 8 comments
Labels
feature New feature or request needs-api changes to Databricks Platform APIs are required

Comments

@vadivelselvaraj
Copy link

Need support for creating the below resources via Terraform.

  • Create SQL Alerts.
  • Configure Data Alerts destination.
@vadivelselvaraj vadivelselvaraj changed the title [FEAT] Provider issue [FEAT] Support for SQL Alerts and Destination Feb 23, 2022
@bryan-vgw
Copy link

bryan-vgw commented Mar 21, 2022

Hey, could I please check the status of this?

@nfx
Copy link
Contributor

nfx commented Mar 21, 2022

Not enough customer interest for this yet

@nfx nfx added the feature New feature or request label Mar 29, 2022
@nicolai86
Copy link
Contributor

@nfx how do you gauge that? 👍 on the tickets?

@zeemaleki
Copy link

@nfx where do you ask customers what they are interested?

@alexott alexott added the needs-api changes to Databricks Platform APIs are required label Jun 20, 2022
@thetkoseek
Copy link

+1 need this also - when apis available

@vadivelselvaraj
Copy link
Author

I see that the webhook integration available in the Data Science & Engineering environment > Admin Console > Notification Destinations also re-uses the same SQL Env's Alert destination.

I hope this new feature would have opened up the APIs.

@nfx Can you confirm?

@alexott
Copy link
Contributor

alexott commented Jan 10, 2023

No, APIs for alert destinations aren't published yet. And most probably work on Alerts will be done only after migration to a Databricks Go SDK to avoid re-implementing the existing code

@alexott
Copy link
Contributor

alexott commented Jul 4, 2024

Closing this in favor of #1983 as Alerts are already implemented

@alexott alexott closed this as completed Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request needs-api changes to Databricks Platform APIs are required
Projects
None yet
Development

No branches or pull requests

7 participants