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.

Sign up for GitHub

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

[AutoPR sql/resource-manager] Update Vulnerability Assessment swaggers #3741

Merged
merged 2 commits into from
Nov 6, 2018
Merged

[AutoPR sql/resource-manager] Update Vulnerability Assessment swaggers #3741

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2cae80
Generated from 63e4176e8577c1abaf1a1496628dc432c7fa5479
AutorestCI Nov 4, 2018
1c65dc0
Generated from 63e4176e8577c1abaf1a1496628dc432c7fa5479
AutorestCI Nov 6, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -118,10 +118,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy_py3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -118,10 +118,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,10 +93,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -119,10 +119,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy_py3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,10 +93,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -119,10 +119,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,10 +93,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -119,10 +119,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy_py3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,10 +93,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -119,10 +119,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,10 +90,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -116,10 +116,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
8 changes: 4 additions & 4 deletions azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy_py3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,10 +90,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
RECEIVE
REFERENCES
The general form for defining an action to be audited is:
<action> ON <object> BY <principal>
{action} ON {object} BY {principal}
Note that <object> in the above format can refer to an object like a
table, view, or stored procedure, or an entire database or schema. For the
latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
used, respectively.
For example:
SELECT on dbo.myTable by public
Expand All @@ -116,10 +116,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
'SQLSecurityAuditEvents' diagnostic logs category on the database should
be also created.
Note that for server level audit you should use the 'master' database as
<databaseName>.
{databaseName}.
Diagnostic Settings URI format:
PUT
https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
For more information, see [Diagnostic Settings REST
API](https://go.microsoft.com/fwlink/?linkid=2033207)
or [Diagnostic Settings
Expand Down
Loading