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

Compute 2019-07-01 version #7094

Merged
merged 23 commits into from
Oct 20, 2019
Merged

Compute 2019-07-01 version #7094

merged 23 commits into from
Oct 20, 2019

Conversation

hyonholee
Copy link
Contributor

@hyonholee hyonholee commented Aug 31, 2019

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.

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Aug 31, 2019

In Testing, Please Ignore

[Logs] (Generated from 4c1f44f, Iteration 34)

Failed .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Succeeded Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Failed Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]
  • Failed compute/resource-manager/v2017_03_30 [Logs]
  • Failed compute/resource-manager/v2017_09_01 [Logs]
  • Failed compute/resource-manager/v2017_12_01 [Logs]
  • Failed compute/resource-manager/v2018_04_01 [Logs]
Failed JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Succeeded Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Succeeded Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

@hyonholee hyonholee added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Aug 31, 2019
@AutorestCI
Copy link

AutorestCI commented Aug 31, 2019

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#8068

@AutorestCI
Copy link

AutorestCI commented Aug 31, 2019

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#6091

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@hyonholee
Copy link
Contributor Author

@zikalino Could you check why model validation fails in this PR? Thanks

@@ -196,6 +196,20 @@ directive:
- ACS service is deprecated so a PATCH endpoint won't be implemented

```
### Tag: package-2019-07

Choose a reason for hiding this comment

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

i think we shoudl just update existing tag instead of creating a new one, or any particular reason for new one?

@zikalino
Copy link

The reason for failure is:

publicipaddressconfiguration in CreateAScaleSetWithAnAzureLoadBalancer.json

@zikalino zikalino added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Oct 17, 2019
@zikalino
Copy link

@hyonholee so we need to disable these validation errors

@qiaozha
Copy link
Member

qiaozha commented Oct 17, 2019

@hyonholee For errors in LintDiff, if you'd like to suppress these validation errors, you may refer to specification/compute/resource-manager/readme.md of this repo and add them to the suppress part.

@hyonholee
Copy link
Contributor Author

@qiaozha @zikalino Thanks, I updated readme.md file to suppress the errors.

Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

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

All swagger API specs should have a "default" response with a response body aligned to standard error contract. Can we at least add that in new/changed APIs?

@KrisBash KrisBash added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label Oct 18, 2019
@hyonholee hyonholee force-pushed the compute-2019-07 branch 3 times, most recently from a6358d4 to 5e46bff Compare October 19, 2019 21:43
@hyonholee
Copy link
Contributor Author

@KrisBash I added default responses to the new APIs.

Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

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

LGTM thanks

@KrisBash KrisBash added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Oct 19, 2019
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.