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

[Maps] Review request for Microsoft.Maps/Microsoft.Maps to add version preview/2.0 #14694

Closed
wants to merge 211 commits into from

Conversation

propheel
Copy link
Contributor

@propheel propheel commented Jun 7, 2021

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

Changelog

Please ensure to add changelog with this PR by answering the following questions.

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No, no need to refresh for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

  • Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

    • Adding new API(s)
    • Adding a new API version
    • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
    • Adding a new service
  • Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

@tjprescott
Copy link
Member

tjprescott commented Jun 9, 2021

@propheel how is this different from #14625?

@propheel
Copy link
Contributor Author

propheel commented Jun 9, 2021

@propheel how is this different from #14625?

@tjprescott this PR is a modification of current Swagger for all 17 Maps services so that the code is actually generated and AutoRest does not complain about the model anymore. The #14625 just adds a new 2.1 version of the Render service.

Comment on lines -379 to -384
"MapTileResultv2": {
"description": "The tile returned from a successful API call.",
"type": "string",
"format": "binary",
"readOnly": true
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This definition is still being referenced above. Should it be kept?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You mean MapTileResultv2? It's not referenced anymore since 200 response definition was changed to describe a file as a response.

Copy link
Contributor

Choose a reason for hiding this comment

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

I see. I thought the response still referenced this as a schema. My mistake.

propheel and others added 4 commits June 11, 2021 11:00
…eturn 200 directly (202 instead) the TS codegen takes 200 definition for the response type, so it is needed to deserialize.
…ue to invalid deserialization of base class properties only
@propheel
Copy link
Contributor Author

propheel commented Jul 2, 2021

The direction of the changes moved to #14871

@propheel propheel closed this Jul 2, 2021
@markweitzel markweitzel added the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Jul 9, 2021
@markweitzel markweitzel removed the APIStewardshipBoard-ReviewRequested This should be reviewed by the Azure API Stewardship team in partnership with the service team. label Jul 30, 2021
@markweitzel markweitzel removed the Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review label Sep 23, 2021
@markweitzel markweitzel changed the title [Hub Generated] Review request for Microsoft.Maps/Microsoft.Maps to add version preview/2.0 [Maps] Review request for Microsoft.Maps/Microsoft.Maps to add version preview/2.0 Oct 12, 2021
@czubair czubair added the APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. label Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants