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

Update readme.md #2922

Merged
merged 1 commit into from
Jun 15, 2021
Merged

Update readme.md #2922

merged 1 commit into from
Jun 15, 2021

Conversation

dw511214992
Copy link

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

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.

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Jun 15, 2021

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.
️🔄CredScan inProgress [Detail]
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Posted by Swagger Pipeline | How to fix these errors?

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Jun 15, 2021

Swagger Generation Artifacts

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

Breaking Changes Tracking

️✔️azure-sdk-for-go - preview/iotspaces/mgmt/2017-10-01-preview/iotspaces - v55.1.0
️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs]Release - Generate from 6c93aed. SDK Automation 14.0.0
    warn	Skip initScript due to not configured
    command	sudo apt-get install -y dotnet-sdk-5.0
    command	autorest --version=V2 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION [email protected]/[email protected] --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/iotspaces/resource-manager/readme.md
    cmderr	[Autorest] realpath(): Permission denied
    cmderr	[Autorest] realpath(): Permission denied
    cmderr	[Autorest] realpath(): Permission denied
    cmderr	[Autorest] realpath(): Permission denied
    cmderr	[Autorest] realpath(): Permission denied
    cmderr	[Autorest] realpath(): Permission denied
  • ️✔️Microsoft.Azure.Management.IoTSpaces [View full logs]  [Release SDK Changes]
    warn	Skip artifact folder because it doesn't exist: artifacts/packages
️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs]Release - Generate from 6c93aed. SDK Automation 14.0.0
    command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
    command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
  • ️✔️preview/iotspaces/mgmt/2017-10-01-preview/iotspaces [View full logs]  [Release SDK Changes]
    info	[Changelog] No exported changes
️️✔️ azure-sdk-for-js-track2 succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

@dw511214992 dw511214992 merged commit 6c93aed into master Jun 15, 2021
dw511214992 added a commit that referenced this pull request Jun 15, 2021
dw511214992 added a commit that referenced this pull request Jun 15, 2021
azure-sdk pushed a commit that referenced this pull request Jun 16, 2021
azure-sdk pushed a commit that referenced this pull request Jun 16, 2021
azure-sdk pushed a commit that referenced this pull request Jun 18, 2021
azure-sdk pushed a commit that referenced this pull request Jun 18, 2021
azure-sdk pushed a commit that referenced this pull request Jun 19, 2021
azure-sdk pushed a commit that referenced this pull request Jun 19, 2021
azure-sdk pushed a commit that referenced this pull request Jun 21, 2021
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Jul 21, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
azure-sdk pushed a commit that referenced this pull request Aug 9, 2022
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.

1 participant