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 VA support for manged instance - Update readme.md #4057

Merged
merged 1 commit into from
Oct 4, 2018
Merged

Adding VA support for manged instance - Update readme.md #4057

merged 1 commit into from
Oct 4, 2018

Conversation

talhers
Copy link
Member

@talhers talhers commented Oct 2, 2018

Update readme.md to support Vulnerability Assessment APIs on managed instance.

The Vulnerability Assessment APIs on managed instance are approved and the PR can be found here.

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@talhers
Copy link
Member Author

talhers commented Oct 2, 2018

@yaakoviyun @yoavfr @jaredmoo for reference

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-java

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

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Oct 2, 2018

Automation for azure-sdk-for-node

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

@annatisch
Copy link
Member

Thanks @talhers - changes look fine to me.
Just to confirm that this means you're ready for these operations to be published in your SDKs?

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.

SDK change is in review at Azure/azure-sdk-for-net#4821

@annatisch annatisch merged commit 491ba55 into Azure:master Oct 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants