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

[App Service] Update swagger spec for ANT80 #5111

Merged
merged 4 commits into from
Feb 13, 2019

Conversation

nking-1
Copy link

@nking-1 nking-1 commented Jan 29, 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.

@nking-1 nking-1 requested a review from naveedaz as a code owner January 29, 2019 22:53
@openapi-portal-comment
Copy link

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

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

Automation for azure-sdk-for-js

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

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

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#2218

@AutorestCI
Copy link

AutorestCI commented Jan 29, 2019

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#2184

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

Copy link
Contributor

@nschonni nschonni left a comment

Choose a reason for hiding this comment

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

Looks like some spelling fixes are being reverted. Maybe they still need to be fixed in the source code

@@ -225,7 +225,7 @@
],
"responses": {
"200": {
"description": "Successfully deleted certificate."
"description": "Succesfully deleted certificate."
Copy link
Contributor

Choose a reason for hiding this comment

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

Succesfully -> Successfully

{
"name": "recommendationId",
"in": "query",
"description": "The GUID of the recommedation object if you query an expired one. You don't need to specify it to query an active entry.",
Copy link
Contributor

Choose a reason for hiding this comment

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

recommedation -> recommendation

"schema": {
"$ref": "./CommonDefinitions.json#/definitions/Operation"
}
"description": "Succesfully deleted virtual network."
Copy link
Contributor

Choose a reason for hiding this comment

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

Succesfully -> Successfully

],
"responses": {
"200": {
"description": "Succesfully deleted virtual network."
Copy link
Contributor

Choose a reason for hiding this comment

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

Succesfully -> Successfully

@@ -354,7 +354,7 @@
},
"expirationDate": {
"format": "date-time",
"description": "Certificate expiration date.",
"description": "Certificate expriration date.",
Copy link
Contributor

Choose a reason for hiding this comment

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

expriration -> expiration

@nking-1
Copy link
Author

nking-1 commented Jan 30, 2019

Looks like some spelling fixes are being reverted. Maybe they still need to be fixed in the source code

Oops, I tried not to copy those over, but it looks like a few got through. Yesterday I combed through the source code to clean up the typos that had been manually fixed in the swagger spec.

Copy link
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

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

What's the reason for breaking changes in stable API versions? Usually, we don't allow to do this.

https://travis-ci.org/Azure/azure-rest-api-specs/jobs/486714248

@nking-1
Copy link
Author

nking-1 commented Feb 1, 2019

My previous commits removed the 2018-02-01 Certificates files but I have added them back and that seems to have fixed the breaking changes check.

There is one expected breaking change. There is a property called adminSiteName that's being hidden in this update. Per @suwatch - Admin Site Name feature never released. We should exclude that from rest api documentation as we might get more questions / affects other features.

@sergey-shandar sergey-shandar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Feb 1, 2019
@nking-1
Copy link
Author

nking-1 commented Feb 6, 2019

@sergey-shandar Is there an ARM team member added to review this PR? This PR has gone dark for about a week now.

@sergey-shandar
Copy link
Contributor

@Nking92 because it's potential breaking changes, ARM should review it before I merge. @ravbhatnagar

@sergey-shandar sergey-shandar added the ARM-overdue ARM review has not occurred within the expected timeframe label Feb 13, 2019
@sergey-shandar sergey-shandar merged commit 27361a7 into Azure:master Feb 13, 2019
veronicagg pushed a commit that referenced this pull request Feb 20, 2019
* Update swagger spec for ANT80

* Fix some spelling errors that were reverted by previous commit

* Move certificate examples to new API version folder

* Add the 2018-02-01 certificates files back
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARM-overdue ARM review has not occurred within the expected timeframe potential-sdk-breaking-change WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants