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

[DO NOT MERGE] VA List Api version edit #4257

Merged
merged 5 commits into from
Oct 31, 2018
Merged

[DO NOT MERGE] VA List Api version edit #4257

merged 5 commits into from
Oct 31, 2018

Conversation

t-robalt
Copy link
Contributor

@t-robalt t-robalt commented Oct 18, 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

@t-robalt
Copy link
Contributor Author

@talhers @yaakoviyun

@AutorestCI
Copy link

AutorestCI commented Oct 18, 2018

Automation for azure-sdk-for-js

A PR has been created for you:
Azure/azure-sdk-for-js#367

@AutorestCI
Copy link

AutorestCI commented Oct 18, 2018

Automation for azure-sdk-for-python

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Oct 18, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Oct 18, 2018

Automation for azure-sdk-for-go

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

@dsgouda
Copy link
Contributor

dsgouda commented Oct 18, 2018

Reassigning due to some other deliverables

@@ -3,7 +3,7 @@
"subscriptionId": "00000000-1111-2222-3333-444444444444",
"resourceGroupName": "vulnerabilityaseessmenttest-4799",
"serverName": "vulnerabilityaseessmenttest-6440",
"databaseName": "testdb",
"databaseName": "testdb",
Copy link
Contributor

Choose a reason for hiding this comment

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

indentation

@jianghaolu
Copy link
Contributor

@t-robalt LGTM - but what's the purpose of deleting a bunch of examples?

@t-robalt
Copy link
Contributor Author

t-robalt commented Oct 24, 2018

@jianghaolu The List method of database and managed database moved to other api-versions, and there aren't any database nor managed database controllers at all in 2018-06-01 so their examples are no longer necessary there.

@AutorestCI
Copy link

AutorestCI commented Oct 24, 2018

Automation for azure-sdk-for-ruby

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-ruby#1792

@AutorestCI
Copy link

AutorestCI commented Oct 31, 2018

Automation for azure-sdk-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:
Azure/azure-sdk-for-java#2138

@dsgouda
Copy link
Contributor

dsgouda commented Nov 1, 2018

@jianghaolu @jaredmoo was this supposed to be merged?

@yaakoviyun
Copy link
Member

yaakoviyun commented Nov 1, 2018 via email

@dsgouda
Copy link
Contributor

dsgouda commented Nov 1, 2018

Thanks for confirming, I was concerned because of the title of the PR 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants