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

[Hub Generated] Review request for Microsoft.DocumentDB to add version stable/2021-01-15 #12261

Merged
merged 35 commits into from
Feb 12, 2021

Conversation

kristynhamasaki
Copy link
Contributor

@kristynhamasaki kristynhamasaki commented Dec 30, 2020

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.
    Changes will be in Prod hopefully by end of January.

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

  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    N/A

    • 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:

  • I commit to follow the Breaking Change Policy of “no breaking changes
  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?
    Please give us an exception for linting failure "RequiredSystemDataInNewApiVersions" We are committed to incorporate this change in Cobalt and many changes in this PR are time critical.

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-workflow-bot
Copy link

Hi, @kristynhamasaki 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.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • 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. vsswagger@microsoft.com

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Dec 30, 2020

    Swagger Validation Report

    ️⌛BreakingChange pending [Detail]
    ️⌛LintDiff pending [Detail]
    ️⌛Avocado pending [Detail]
    ️⌛ModelValidation pending [Detail]
    ️⌛SemanticValidation pending [Detail]
    ️⌛[Staging] Cross Version BreakingChange (Base on preview version) pending [Detail]
    ️🔄[Staging] Cross Version BreakingChange (Base on stable version) inProgress [Detail]
    ️⌛CredScan pending [Detail]
    ️⌛[Staging] SDK Track2 Validation pending [Detail]
    ️⌛[Staging] PrettierCheck pending [Detail]
    ️⌛[Staging] SpellCheck pending [Detail]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Dec 30, 2020

    Swagger Generation Artifacts

    ️🔄[Staging] ApiDocPreview inProgress [Detail]
    Posted by Swagger Pipeline | How to fix these errors?

    @kristynhamasaki
    Copy link
    Contributor Author

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    @openapi-workflow-bot
    Copy link

    Hi @kristynhamasaki, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff.

    TaskHow to fixPrioritySupport (Microsoft alias)
    AvocadoFix-AvocadoHighruowan
    Semantic validationFix-SemanticValidation-ErrorHighraychen, jianyxi
    Model validationFix-ModelValidation-ErrorHighraychen,jianyxi
    LintDiffFix-LintDiffhighjianyxi, ruoxuan
    If you need further help, please feedback via swagger feedback."

    Akashdeep Goel and others added 2 commits January 14, 2021 13:47
    Update sql partition key kind and adds systemKey field
    @kristynhamasaki kristynhamasaki removed the DoNotMerge <valid label in PR review process> use to hold merge after approval label Feb 10, 2021
    @tjprescott tjprescott merged commit a1eee04 into Azure:master Feb 12, 2021
    This was referenced Feb 12, 2021
    mkarmark pushed a commit to mkarmark/azure-rest-api-specs that referenced this pull request Jul 21, 2021
    …n stable/2021-01-15 (Azure#12261)
    
    * Adds base for updating Microsoft.DocumentDB from version stable/2020-09-01 to version 2021-01-15
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * Changes to examples
    
    * add real example to patcH
    
    * add to patch
    
    * Update sql partition key kind and adds systemKey field
    
    * Refactor cosmosdb.json + examples with updated property
    
    * Adds examples to list call
    
    * Fix partition key
    
    * Managed Service Identity Support
    
    * Fix pk version
    
    * Changes for private endpoint and enums
    
    * Update readme
    
    * Fixes for private endpoint
    
    * Fix api version
    
    * Add 4.0 to ApiProperties enum
    
    * Add suppression for RequiredSystemDataInNewApiVersions
    
    * Fix Managed Service Identity
    
    * Update examples
    
    * Managed Service Identity Fix
    
    * Add new version to other readmes
    
    * Fix output path for go version 01-15
    
    * Fix output path for go version 01-15 again
    
    * msi fix
    
    * Fix examples for MSI
    
    * Change NetworkAclBypass to modelAsString=false
    
    * Remove duplicate ErrorResponse
    
    Co-authored-by: Akashdeep Goel <akgoe@microsoft.com>
    Co-authored-by: xujin-zhang <xujin_zhang@outlook.com>
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review CI-BreakingChange-Go CI-BreakingChange-Python
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    CosmosDB Compound Index Sort Order returns incorrect case for CompositePathSortOrder in Get
    7 participants