-
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
Add DatabaseVulnerabilityAssessments swagger #3275
Conversation
The put api is updated. A new parameter is added to its body properties storageAccountAccessKey. storageContainerSasKey isn't required anymore, but the user must to specified one of the following parameters: storageContainerSasKey or storageAccountAccessKey
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goEncountered a Subprocess error: (azure-sdk-for-go)
Command: dep ensure grouped write of manifest, lock and vendor: error while writing out vendor tree: failed to write dep tree: failed to export golang.org/x/text: failed to fetch source for https://go.googlesource.com/text: unable to get repository: Cloning into '/tmp/tmpdvcqqc9a/pkg/dep/sources/https---go.googlesource.com-text'...
fatal: unable to access 'https://go.googlesource.com/text/': Failed to connect to go.googlesource.com port 443: Connection timed out
: command failed: [git clone --recursive -v --progress https://go.googlesource.com/text /tmp/tmpdvcqqc9a/pkg/dep/sources/https---go.googlesource.com-text]: exit status 128 |
Automation for azure-sdk-for-nodeA PR has been created for you: |
Please look at travis CI failures |
Are api-versions other than 2017-10 affected? |
Hi.
|
Let me rephrase my question. Here you are adding api-version 2017-10, but does api-version 2017-03 or earlier also contain the change? |
add storageContainerPath to properties as optional parameters
@@ -261,12 +271,44 @@ | |||
} | |||
} | |||
}, | |||
"Resource": { |
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 remove
"DatabaseVulnerabilityAssessment": { | ||
"description": "A database vulnerability assessment.", | ||
"type": "object", | ||
"allOf": [ | ||
{ | ||
"$ref": "../../../common/v1/types.json#/definitions/ProxyResource" | ||
"$ref": "#/definitions/ProxyResource" |
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
-
"$ref": "../../../common/v1/types.json#/definitions/ProxyResource"
] | ||
}, | ||
"storageAccountAccessKey": { | ||
"description": "Specifies the identifier key of the auditing storage account. If 'StorageContainerSasKey' isn't specified, storageAccountAccessKey is required.", | ||
"type": "string", | ||
"x-ms-mutability": [ | ||
"create", |
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.
-
"create",
-
"update"?
This reverts commit 7f90a83.
This reverts commit 9f34855.
This reverts commit 660b2f7.
The put api is updated. A new parameter is added to its body properties storageAccountAccessKey. storageContainerSasKey isn't required anymore, but the user must to specified one of the following parameters: storageContainerSasKey or storageAccountAccessKey
Hi.
|
Looks good. |
@jaredmoo - We talked on it. It due to moved one field to be optional. |
clean databaseVulnerabilityAssessmentScans
Hi @ravbhatnagar and @jaredmoo - our API id deployed world wide. Could you merge this pull request? |
There is still model validation error: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/397699547 |
fixed |
@jaredmoo That's a preview Swagger, signed-of by ARM, and changes look good me. Once you think it's done, let me know and I merge the Pr. |
The put api is updated.
A new parameter is added to its body properties storageAccountAccessKey.
storageContainerSasKey isn't required anymore, but the user must to specified one of the following parameters:
storageContainerSasKey
or
storageAccountAccessKey
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