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.

Sign up for GitHub

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

Jump to bottom

Update description of computerName in old version. #5155

Closed

hyonholee wants to merge 0 commits into Azure:master from hyonholee:sync

Contributor

hyonholee commented Feb 5, 2019 •

edited

Loading

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

I have reviewed the documentation for the workflow.
Validation tools were run on swagger spec(s) and have all been fixed in this PR.
The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

ghost commented Feb 5, 2019

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

Contributor

azuresdkci commented Feb 5, 2019

Can one of the admins verify this patch?

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-js

Unable to detect any generation context from this PR.

AutorestCI mentioned this pull request

[AutoPR compute/resource-manager] Update description of computerName in old version. Azure/azure-sdk-for-ruby#2204

Closed

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-ruby

Unable to detect any generation context from this PR.

azuresdkci assigned anuchandy

azuresdkci requested a review from anuchandy

February 5, 2019 00:03

AutorestCI mentioned this pull request

[AutoPR compute/resource-manager] Update description of computerName in old version. Azure/azure-sdk-for-python#4306

Closed

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-python

Unable to detect any generation context from this PR.

AutorestCI mentioned this pull request

[AutoPR compute/resource-manager] Update description of computerName in old version. Azure/azure-sdk-for-go#4022

Closed

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-go

Unable to detect any generation context from this PR.

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-node

Unable to detect any generation context from this PR.

AutorestCI commented Feb 5, 2019 •

edited

Loading

Automation for azure-sdk-for-java

Unable to detect any generation context from this PR.

hyonholee closed this

hyonholee force-pushed the sync branch from 386d965 to 27ad7f3 Compare

March 7, 2019 07:21

mccleanp pushed a commit that referenced this pull request


          Changed the provider folder name (#5155)

1f21fc0

* PrettyCheck fix DeleteVMMServer.json

* PrettyCheck files in examples

* git go sdk track 2

* Correcting the format

* Changing provider folder name to camel case

* Corresponding chnages to readme.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet