Skip to content

Conversation

@maorleger
Copy link
Member

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

Changelog

Add a changelog entry for 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 are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the 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 refresh required 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

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
  • 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a 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.

@openapi-workflow-bot
Copy link

Hi, @maorleger 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. [email protected]

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 28, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️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.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 28, 2022

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
    ️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking

    Posted by Swagger Pipeline | How to fix these errors?

    @maorleger
    Copy link
    Member Author

    @heaths not sure why pipeline is pending for public.rest-api-specs - do you know who owns this pipeline or who I can reach out to?

    @heaths
    Copy link
    Member

    heaths commented Mar 1, 2022

    According to https://github.com/Azure/azure-rest-api-specs/pull/18031/checks?check_run_id=5366659603 it completed. Seems to be an AzDO/GitHub interaction issue. I've seen these too many times before.

    @lmazuel can you merge this so we can proceed with the Key Vault / Managed HSM swagger GA?

    @maorleger maorleger force-pushed the dev-keyvault-Microsoft.KeyVault-7.3-suppress-cspell branch from c5fb4a5 to abf03f1 Compare March 2, 2022 22:55
    @maorleger
    Copy link
    Member Author

    @lmazuel friendly ping - would you mind merging this for us? The builds all pass, just seems that GH isn't getting updated...

    @heaths
    Copy link
    Member

    heaths commented Mar 3, 2022

    /azp run public.rest-api-specs

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @heaths
    Copy link
    Member

    heaths commented Mar 3, 2022

    @akning-ms the public.rest-api-specs pipeline, despite succeeding, is not reporting back status rather frequently. On this PR it's been twice. I restarted the pipeline and it again completed successfully. Can someone from your team look into this? As the only "error" preventing checks from passing, I cannot merge this and we have to have admins do it.

    @lmazuel can you please merge this? Despite what checks show here, if you go to the checks tab itself it shows all pipelines passed. Unfortunately, that's not enough to allow me to merge it. This will hold up our KV release.

    @kurtzeborn kurtzeborn merged commit c25e398 into Azure:dev-keyvault-Microsoft.KeyVault-7.3 Mar 3, 2022
    lmazuel pushed a commit that referenced this pull request Mar 21, 2022
    …stable/7.3 (#18028)
    
    * Adds base for updating Microsoft.KeyVault from version preview/7.3-preview to version 7.3
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * [KeyVault] - Add exclusion for known spellcheck issue (#18031)
    
    * add exclusion for known spellcheck issue
    
    * collapse cspell ignore for keyvault's storage.json
    FredericHeem pushed a commit to grucloud/azure-rest-api-specs that referenced this pull request May 16, 2022
    …stable/7.3 (Azure#18028)
    
    * Adds base for updating Microsoft.KeyVault from version preview/7.3-preview to version 7.3
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * [KeyVault] - Add exclusion for known spellcheck issue (Azure#18031)
    
    * add exclusion for known spellcheck issue
    
    * collapse cspell ignore for keyvault's storage.json
    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