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

Add serverSecurityAlertPolicies APIs for MySQL servers #3644

Merged
merged 1 commit into from
Aug 22, 2018
Merged

Add serverSecurityAlertPolicies APIs for MySQL servers #3644

merged 1 commit into from
Aug 22, 2018

Conversation

ayeletshpigelman
Copy link
Contributor

@ayeletshpigelman ayeletshpigelman commented Aug 15, 2018

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

@AutorestCI
Copy link

AutorestCI commented Aug 15, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3182

@AutorestCI
Copy link

AutorestCI commented Aug 15, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Aug 15, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#3399

@AutorestCI
Copy link

AutorestCI commented Aug 15, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2339

@AutorestCI
Copy link

AutorestCI commented Aug 15, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#2514

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azuresdkci azuresdkci requested a review from anuchandy August 15, 2018 13:23
@anuchandy anuchandy added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 15, 2018
@anuchandy anuchandy requested a review from ravbhatnagar August 15, 2018 17:03
Copy link
Member

@anuchandy anuchandy left a comment

Choose a reason for hiding this comment

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

@ravbhatnagar please review the part referring storage account. Looks good from SDK side.

"enum": [
"default"
],
"x-ms-parameter-location": "method"
Copy link
Member

Choose a reason for hiding this comment

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

It seems this definition is not used anywhere if so please remove it.

"storageAccountAccessKey": {
"description": "Specifies the identifier key of the Threat Detection audit storage account.",
"type": "string"
},
Copy link
Member

Choose a reason for hiding this comment

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

My understanding is ARM usually recommend to refer storage account using the fully qualified ARM resource id. This requires service to have linked access to storage that way service can reliably ensure there are sufficient permission to perform the operation (such as reading keys). Adding @ravbhatnagar from ARM team to comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is similar in all our APIs for Postgres, SQL and Managed Instance
https://github.com/Azure/azure-rest-api-specs/pull/2947/files

@ayeletshpigelman
Copy link
Contributor Author

@ravbhatnagar please review
It is urgent for Ignite
thank you!

@anuchandy
Copy link
Member

@ayeletshpigelman whats your contact email? need to start an email thread with ARM with you in loop.

@ayeletshpigelman
Copy link
Contributor Author

[email protected]

Copy link
Contributor

@ravbhatnagar ravbhatnagar left a comment

Choose a reason for hiding this comment

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

One minor note.

@@ -1062,6 +1062,126 @@
}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}/securityAlertPolicies/{securityAlertPolicyName}": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Should there be an API to list the collection of securityPOlicies under a server.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is only one policy, but the user can define its name.

@ayeletshpigelman
Copy link
Contributor Author

@anuchandy can you please merge the pull request

@anuchandy anuchandy merged commit 05b9819 into Azure:master Aug 22, 2018
@anuchandy anuchandy 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 Aug 22, 2018
jhendrixMSFT added a commit to Azure/azure-sdk-for-go that referenced this pull request Aug 22, 2018
jhendrixMSFT pushed a commit to Azure/azure-sdk-for-go that referenced this pull request Aug 22, 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.

5 participants