-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
SQL Database Security Alert Policies API (2014-04-01) In-Idempotent Behavior of userServerDefault
#9762
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub. |
Any progress on this one? |
Just confirmed this problem still exists, any progress yet? |
@weidongxu-microsoft Please take a look at this issue, it breaks for a long time.. |
@azureSQLGitHub any update? |
useServerDefault is a deprecated property. please ignore it. Moreover, we recommend using API version 2018-06-01-preview for QL Database Security Alert Policies |
@magodo Thanks for your feedback! |
SQL Database Security Alert Policies API version 2014-04-01 has property called
useServerDefault
in theDatabaseSecurityAlertPolicyProperties
. From swagger definition, this property accepts either "Enabled" or "Disabled". So if I define the security alert policy in SQL Server, invoke the following request, which specifies this property asEnabled
:Then if I invoke a GET right after, the
useServerDefault
is changed intoDisabled
.This behavior makes IaC tools that depend on the idempotency of API hard to implement.
The text was updated successfully, but these errors were encountered: