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

Adding database vulnerability assessmen scan APIs #2418

Merged
merged 10 commits into from
May 7, 2018
Merged

Adding database vulnerability assessmen scan APIs #2418

merged 10 commits into from
May 7, 2018

Conversation

yaakoviyun
Copy link
Member

@yaakoviyun yaakoviyun commented Feb 5, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

Adding database vulnerability assessmen scan APIs
@AutorestCI
Copy link

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']
Finished with return code 1
and output:

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'.

@AutorestCI
Copy link

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']
Finished with return code 1
and output:

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'.

@AutorestCI
Copy link

Did a commit to Azure/azure-sdk-for-python:
Azure/azure-sdk-for-python@0e285bf

@AutorestCI
Copy link

Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-go)

Command: gofmt -w ./services/
Finished with return code 2
and output:

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

@AutorestCI
Copy link

Did a commit to Azure/azure-sdk-for-python:
Azure/azure-sdk-for-python@3ea5e06

@azuresdkciprbot
Copy link

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: specification/sql/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@AutorestCI
Copy link

Swagger to SDK encountered a Subprocess error: (Azure/azure-sdk-for-go)

Command: gofmt -w ./services/
Finished with return code 2
and output:

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"
]
},
Copy link
Member

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

Copy link
Member Author

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."
Copy link
Member

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?

Copy link
Member Author

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"
Copy link
Member

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

@anuchandy anuchandy added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Feb 5, 2018
@anuchandy
Copy link
Member

@yaakoviyun thanks for the response. @ravbhatnagar please sign-off since this is a new spec.

@anuchandy
Copy link
Member

@yaakoviyun Could you share your MS alias, wanted to start an email thread but could't locate your name/alias.

@anuchandy
Copy link
Member

@ravbhatnagar ping

@anuchandy
Copy link
Member

@ravbhatnagar can you please take a look?

}
}
},
"post": {
Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Contributor

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

Copy link
Member Author

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.

Copy link
Member Author

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

@ravbhatnagar
Copy link
Contributor

Just one comment around the use of POST instead of PUT.

@ravbhatnagar
Copy link
Contributor

@yaakoviyun

@anuchandy
Copy link
Member

@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
@AutorestCI
Copy link

AutorestCI commented Feb 28, 2018

Automation for azure-sdk-for-python

A 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:
Azure/azure-sdk-for-python#2285

@AutorestCI
Copy link

AutorestCI commented Feb 28, 2018

Automation for azure-sdk-for-go

A 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:
Azure/azure-sdk-for-go#1741

@yaakoviyun
Copy link
Member Author

yaakoviyun commented Mar 4, 2018 via email

@yaakoviyun
Copy link
Member Author

@ravbhatnagar can you take a look?

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Mar 9, 2018
@ravbhatnagar
Copy link
Contributor

Looks good!

@AutorestCI
Copy link

AutorestCI commented Mar 20, 2018

Automation for azure-libraries-for-java

A 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:
AutorestCI/azure-libraries-for-java#9

@AutorestCI
Copy link

AutorestCI commented Mar 20, 2018

Automation for azure-sdk-for-node

A 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:
Azure/azure-sdk-for-node#2715

@@ -468,6 +469,7 @@ batch:
- tag: package-2014-04
```


Copy link
Contributor

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
Copy link
Contributor

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

@anuchandy
Copy link
Member

@yaakoviyun could you address comments from @jaredmoo?

Add new swagger to both package-composite-v1 and -v2 sections, and
package-pure-2017-10-preview
@yaakoviyun
Copy link
Member Author

yaakoviyun commented Apr 15, 2018 via email

@azuresdkciprbot
Copy link

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: specification/sql/resource-manager/readme.md
Before the PR: Warning(s): 24 Error(s): 0
After the PR: Warning(s): 24 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

Copy link
Contributor

@jaredmoo jaredmoo left a 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 :)

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These 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

⚠️0 new Warnings.(6 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These 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

⚠️0 new Warnings.(20 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These 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

⚠️0 new Warnings.(20 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These 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

⚠️0 new Warnings.(6 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@yaakoviyun
Copy link
Member Author

ping, can you merge?

@jaredmoo
Copy link
Contributor

@yaakoviyun There are merge conflicts again. Can you resolve?

@ravbhatnagar it looks like you signed off in comments, can you approve?

@azuresdkciprbot
Copy link

AutoRest linter results for SDK Related Validation Errors/Warnings

These 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

⚠️1 new Warnings.(21 total)
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.

@azuresdkciprbot
Copy link

AutoRest linter results for ARM Related Validation Errors/Warnings

These 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

⚠️0 new Warnings.(6 total)
0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@yaakoviyun
Copy link
Member Author

ping...

@anuchandy anuchandy merged commit cef11c5 into Azure:master May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants