-
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
Adding database vulnerability assessmen scan APIs #2418
Conversation
Adding database vulnerability assessmen scan APIs
Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-python)
Command: ['/usr/local/bin/autorest', '/tmp/tmpldfb13v7/rest/specification/sql/resource-manager/readme.md', '--multiapi', '--python', '--python-mode=update', '--python-sdks-folder=/tmp/tmpldfb13v7/sdk', '--use=@microsoft.azure/autorest.python@preview', '--version=preview'] AutoRest code generation utility [version: 2.0.4245; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/tmp/.autorest/@microsoft.azure_autorest-core@2.0.4246/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4246)
Loading AutoRest extension '@microsoft.azure/autorest.python' (preview->2.1.34)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
FATAL: swagger-document-override/md-override-loader - FAILED
FATAL: Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 77): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 78): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 79): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 80): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 81): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 82): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 83): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 84): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 85): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 86): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 87): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 88): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 89): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 90): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 91): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 92): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:28065) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 93): Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
FATAL: swagger-document/loader - FAILED
FATAL: Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
Process() cancelled due to exception : Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
Error: Could not read 'file:///tmp/tmpldfb13v7/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'. |
Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-go)
Command: ['/usr/local/bin/autorest', '/tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmp9z0w7fmq/sdk', '--multiapi', '--package-version=v12.2.1-beta', '--use=@microsoft.azure/autorest.go@preview', "--user-agent='Azure-SDK-For-Go/v12.2.1-beta services'", '--verbose'] AutoRest code generation utility [version: 2.0.4244; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
There is a new version of AutoRest available (2.0.4245).
> You can install the newer version with with npm install -g autorest@latest
Loading AutoRest core '/tmp/.autorest/@microsoft.azure_autorest-core@2.0.4244/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4244)
Loading AutoRest extension '@microsoft.azure/autorest.go' (preview->3.0.40)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.1.22->2.1.22)
Processing batch task - {"tag":"package-2017-10-preview"} .
FATAL: swagger-document-override/md-override-loader - FAILED
FATAL: Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 82): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 83): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 84): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 85): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 86): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 87): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 88): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 89): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 90): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 91): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 92): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 93): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 94): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 95): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 96): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 97): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
(node:42377) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 98): Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
FATAL: swagger-document/loader - FAILED
FATAL: Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
Process() cancelled due to exception : Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'.
Failure during batch task - {"tag":"package-2017-10-preview"} -- Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'..
Error: Could not read 'file:///tmp/tmp9z0w7fmq/rest/specification/sql/resource-manager/Microsoft.Sql/preview/2017-10-01-preview/serverDnsAliases.json'. |
Did a commit to Azure/azure-sdk-for-python: |
Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-go)
Command: gofmt -w ./services/ services/sql/mgmt/2014-04-01/sql/models.go:566:8: expected ';', found ':'
services/sql/mgmt/2014-04-01/sql/models.go:571:145: rune literal not terminated
services/sql/mgmt/2014-04-01/sql/models.go:573:98: expected '}', found 'for'
services/sql/mgmt/2014-04-01/sql/models.go:573:150: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:158: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:169: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:193: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:212: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:234: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:246: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:257: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:291: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1177:8: expected ';', found ':'
services/sql/mgmt/2015-05-01-preview/sql/models.go:1182:145: rune literal not terminated
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:98: expected '}', found 'for'
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:150: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:158: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:169: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:193: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:212: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:234: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:246: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:257: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:291: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1433:8: expected ';', found ':'
services/sql/mgmt/2017-03-01-preview/sql/models.go:1438:145: rune literal not terminated
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:98: expected '}', found 'for'
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:150: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:158: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:169: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:193: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:212: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:234: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:246: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:257: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:291: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1461:8: expected ';', found ':'
services/sql/mgmt/2017-10-01-preview/sql/models.go:1466:145: rune literal not terminated
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:98: expected '}', found 'for'
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:150: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:158: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:169: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:193: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:212: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:234: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:246: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:257: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:291: illegal rune literal |
Did a commit to Azure/azure-sdk-for-python: |
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-go)
Command: gofmt -w ./services/ services/sql/mgmt/2014-04-01/sql/models.go:566:8: expected ';', found ':'
services/sql/mgmt/2014-04-01/sql/models.go:571:145: rune literal not terminated
services/sql/mgmt/2014-04-01/sql/models.go:573:98: expected '}', found 'for'
services/sql/mgmt/2014-04-01/sql/models.go:573:150: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:158: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:169: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:193: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:212: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:234: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:246: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:257: illegal rune literal
services/sql/mgmt/2014-04-01/sql/models.go:573:291: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1177:8: expected ';', found ':'
services/sql/mgmt/2015-05-01-preview/sql/models.go:1182:145: rune literal not terminated
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:98: expected '}', found 'for'
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:150: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:158: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:169: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:193: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:212: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:234: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:246: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:257: illegal rune literal
services/sql/mgmt/2015-05-01-preview/sql/models.go:1184:291: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1433:8: expected ';', found ':'
services/sql/mgmt/2017-03-01-preview/sql/models.go:1438:145: rune literal not terminated
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:98: expected '}', found 'for'
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:150: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:158: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:169: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:193: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:212: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:234: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:246: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:257: illegal rune literal
services/sql/mgmt/2017-03-01-preview/sql/models.go:1440:291: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1461:8: expected ';', found ':'
services/sql/mgmt/2017-10-01-preview/sql/models.go:1466:145: rune literal not terminated
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:98: expected '}', found 'for'
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:150: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:158: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:169: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:193: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:212: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:234: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:246: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:257: illegal rune literal
services/sql/mgmt/2017-10-01-preview/sql/models.go:1468:291: illegal rune literal |
"create", | ||
"update" | ||
] | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The storage account should be referenced using the fully qualified ARM resource id instead of passing the url and access-key. You can then enable linked access check on it reliably to ensure sufficient permission are there to perform the operation. Since this is an ARM guideline, tagging Gaurav @ravbhatnagar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already got the approval from ARM to go this way before.
The intention here is that a user will supply a SAS key (not access key) with an expiration date and privileges he chooses to supply.
This way he is more "secure" as we have a SAS key that he controls on.
], | ||
"responses": { | ||
"200": { | ||
"description": "Successfully executed a Vulnerability Assessment database scan." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just confirming, is there any final response that contains the scan id? or it should always be retrieved using DatabaseVulnerabilityAssessmentScans_ListByDatabase
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently to get the scan ID of a past scan, the user should use: DatabaseVulnerabilityAssessmentScans_ListByDatabase
If the user has a scan ID he can use DatabaseVulnerabilityAssessmentScans_Get
"200": { | ||
"description": "Scan result was converted successfully.", | ||
"schema": { | ||
"$ref": "#/definitions/DatabaseVulnerabilityAssessmentScansExport" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If scan result was already converted, does this POST call return that existing result?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
@yaakoviyun thanks for the response. @ravbhatnagar please sign-off since this is a new spec. |
@yaakoviyun Could you share your MS alias, wanted to start an email thread but could't locate your name/alias. |
@ravbhatnagar ping |
@ravbhatnagar can you please take a look? |
} | ||
} | ||
}, | ||
"post": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is a scan not created (initiated) using PUT instead of POST?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put is traditionally used to create a resource. This API is for executing a scan (doing operation on a resource), so we thought POST will be a better match.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yaakoviyun - But this is not modeled as an action on a resource. Should it be modeled like - POST subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/vulnerabilityAssessments/{vulnerabilityAssessmentName}/initiateScan
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK Will make the change in the next API-version of this API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We decided to implement it for this api version
Just one comment around the use of POST instead of PUT. |
@yaakoviyun can you please take a look at the one comment from Gaurav? |
- POST subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/vulnerabilityAssessments/{vulnerabilityAssessmentName}/initiateScan
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
@ravbhatnagar can you take a look? |
Looks good! |
Automation for azure-libraries-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-nodeA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
@@ -468,6 +469,7 @@ batch: | |||
- tag: package-2014-04 | |||
``` | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Undo whitespace
@@ -78,6 +78,7 @@ input-file: | |||
- Microsoft.Sql/preview/2017-03-01-preview/restorePoints.json | |||
- Microsoft.Sql/preview/2017-10-01-preview/cancelOperations.json | |||
- Microsoft.Sql/preview/2017-10-01-preview/cancelPoolOperations.json | |||
- Microsoft.Sql/preview/2017-10-01-preview/databaseVulnerabilityAssessmentScans.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add to both package-composite-v1 and -v2 sections, and package-pure-2017-10-preview
@yaakoviyun could you address comments from @jaredmoo? |
Add new swagger to both package-composite-v1 and -v2 sections, and package-pure-2017-10-preview
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for readme.md changes, since last month there is now a new composite-v3 section. Please add there as well. I am approving now because I am on vacation and might not look at your next commit :)
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
ping, can you merge? |
@yaakoviyun There are merge conflicts again. Can you resolve? @ravbhatnagar it looks like you signed off in comments, can you approve? |
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
Code | Id | Source | Message |
---|---|---|---|
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'initiatescan' in:'DatabaseVulnerabilityAssessmentScans_Execute'. Consider updating the operationId |
❌0 new Errors.(0 total)
AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback
Thanks for your co-operation.
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/sql/resource-manager/readme.md
|
ping... |
Adding database vulnerability assessmen scan APIs
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger