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] Add normalizer to latest preview API #11954

Closed
wants to merge 9 commits into from
Closed

[DO NOT MERGE] Add normalizer to latest preview API #11954

wants to merge 9 commits into from

Conversation

robertklee
Copy link
Member

@robertklee robertklee commented Dec 4, 2020

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

This PR exposes normalizers to the 2020-06-30-Preview API version. The docs links still need to be updated after they are written and published.

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.

early 2021 (@ishansrivastava90 and @Yahnoosh to confirm)

  1. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.

early 2021 (@ishansrivastava90 and @Yahnoosh to confirm)

  1. 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

(@ishansrivastava90 and @Yahnoosh to confirm)

Contribution checklist:

handing off to @ishansrivastava90 (was not able to get autoRest command to work)

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
    • 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 API 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 version with Breaking Change Validation errors
  • Updating API(s) in preview over 1 year

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.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Dec 4, 2020

Swagger Validation Report

️❌BreakingChange: 5 Errors, 0 Warnings failed [Detail]

Rule Message
1041 - AddedPropertyInResponse The new version has a new property 'normalizers' in response that was not found in the old version.
New: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L7034:7
Old: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L6931:7
1041 - AddedPropertyInResponse The new version has a new property 'normalizers' in response that was not found in the old version.
New: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L7034:7
Old: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L6931:7
1041 - AddedPropertyInResponse The new version has a new property 'normalizers' in response that was not found in the old version.
New: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L7034:7
Old: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L6931:7
1041 - AddedPropertyInResponse The new version has a new property 'normalizers' in response that was not found in the old version.
New: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L7034:7
Old: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L6931:7
1041 - AddedPropertyInResponse The new version has a new property 'normalizers' in response that was not found in the old version.
New: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L7034:7
Old: Azure.Search/preview/2020-06-30-Preview/searchservice.json#L6931:7
️️✔️LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.

️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
Posted by Swagger Pipeline | How to fix these errors?

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Dec 4, 2020

Swagger Generation Artifacts

️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
Posted by Swagger Pipeline | How to fix these errors?

@openapi-workflow-bot
Copy link

Hi, @robertklee Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

    @@ -2873,6 +2918,44 @@
    "url": "http://lucene.apache.org/core/4_10_3/analyzers-common/org/apache/lucene/analysis/core/StopAnalyzer.html"
    }
    },
    "CustomNormalizer": {
    "discriminator": "@odata.type",
    Copy link
    Member

    Choose a reason for hiding this comment

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

    There doesn't appear to be any polymorphism here, so why do you need a discriminator? Does our API even require @odata.type for normalizer definitions?

    Copy link
    Member Author

    @robertklee robertklee Dec 4, 2020

    Choose a reason for hiding this comment

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

    you're right, I don't think we need the discriminator right now. I'll remove.

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    We do need @odata.type for normalizer definitions. We only support #Microsoft.Azure.Search.CustomNormalizer right now.

    @brjohnstmsft brjohnstmsft changed the title Add normalizer to latest preview API [DO NOT MERGE] Add normalizer to latest preview API Dec 5, 2020
    @brjohnstmsft
    Copy link
    Member

    Let's hold off on merging this until the API changes are actually deployed.

    @robertklee
    Copy link
    Member Author

    robertklee commented Dec 5, 2020 via email

    @brjohnstmsft
    Copy link
    Member

    Closing this since we're not ready to merge it yet (the feature hasn't been deployed). We'll re-open the PR once the changes are ready.

    @ishansrivastava90
    Copy link
    Contributor

    @brjohnstmsft Can you re-open this PR since the changes are checked in and scheduled for next deployment? It seems that I don't have reopening rights. T

    @robertklee
    Copy link
    Member Author

    robertklee commented Jan 6, 2021

    I don't see a re-open button on my end either. I might have to push an update (probably a rebase) to get the re-open button to show up.

    Edit: rebasing didn't work.

    @brjohnstmsft
    Copy link
    Member

    @ishansrivastava90 @robertklee I don't seem to have re-open rights either, but there's no rush -- This shouldn't be merged until the changes are deployed worldwide.

    @robertklee
    Copy link
    Member Author

    @ishansrivastava90 @brjohnstmsft If you need me, feel free to ping me once you are ready by commenting here. I can open a new PR if re-open isn't working at that point. Exciting that it's going to deployment soon! :)

    @ishansrivastava90 ishansrivastava90 mentioned this pull request Feb 24, 2021
    25 tasks
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants