You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.
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. vscswagger@microsoft.com
[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.
+ Function `BuildServiceAgentPoolClient.UpdatePutPreparer` parameter(s) have been changed from `(context.Context, string, string, string, string, BuildServiceAgentPoolSizeProperties)` to `(context.Context, string, string, string, string, BuildServiceAgentPoolResource)`
+ Function `BuildServiceAgentPoolClient.UpdatePut` parameter(s) have been changed from `(context.Context, string, string, string, string, BuildServiceAgentPoolSizeProperties)` to `(context.Context, string, string, string, string, BuildServiceAgentPoolResource)`
+ Type of `NameAvailabilityParameters.Type` has been changed from `*string` to `Type`
+ Type of `ResourceSku.Name` has been changed from `*string` to `Name`
️✔️Succeeded [Logs] Generate from 841eea9bc785fe94b6de7b0527d58c5c1ed1cf5b. SDK Automation 14.0.0
command sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
warn specification/signalr/resource-manager/readme.md skipped due to azure-powershell not found in swagger-to-sdk
command pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
⚠️Warning [Logs] Generate from 841eea9bc785fe94b6de7b0527d58c5c1ed1cf5b. SDK Automation 14.0.0
command sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
cmderr [automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
command sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
cmderr [automation_generate.sh] npm notice
cmderr [automation_generate.sh] npm notice New minor version of npm available! 8.3.1 -> 8.5.1
cmderr [automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.5.1>
cmderr [automation_generate.sh] npm notice Run `npm install -g npm@8.5.1` to update!
cmderr [automation_generate.sh] npm notice
info [Changelog] **Features**
info [Changelog]
info [Changelog] - Added operation group SkuOperations
info [Changelog]
info [Changelog] **Breaking changes**
info [Changelog]
info [Changelog] - Model OperationDetail no longer has parameter action_type
⚠️Warning [Logs] Generate from 841eea9bc785fe94b6de7b0527d58c5c1ed1cf5b. SDK Automation 14.0.0
command sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
cmderr [automation_init.sh] npm WARN deprecated read-package-tree@5.1.6: The functionality that this package provided is now in @npmcli/arborist
cmderr [automation_init.sh] npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
cmderr [automation_init.sh] npm WARN deprecated @opentelemetry/types@0.2.0: Package renamed to @opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js
cmderr [automation_init.sh] npm notice created a lockfile as package-lock.json. You should commit this file.
cmderr [automation_init.sh] npm WARN @octokit/plugin-request-log@1.0.4 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
warn File azure-sdk-for-js_tmp/initOutput.json not found to read
command sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
Only show 9 items here, please refer to log for details.
info [Changelog] - New function `PossibleTrafficDirectionValues() []TrafficDirection`
info [Changelog] - New function `RequiredTraffic.MarshalJSON() ([]byte, error)`
info [Changelog] - New struct `RequiredTraffic`
info [Changelog] - New field `ToBeExportedForShoebox` in struct `MetricDimension`
info [Changelog] - New field `ActionType` in struct `OperationDetail`
info [Changelog] - New field `SourceMdmNamespace` in struct `MetricSpecification`
info [Changelog] - New field `RequiredTraffics` in struct `NetworkProfile`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 13 additive change(s).
️✔️preview/appplatform/mgmt/2022-01-01-preview/appplatform [View full logs]
info [Changelog] ### Breaking Changes
info [Changelog]
info [Changelog] - Function `BuildServiceAgentPoolClient.UpdatePutPreparer` parameter(s) have been changed from `(context.Context, string, string, string, string, BuildServiceAgentPoolSizeProperties)` to `(context.Context, string, string, string, string, BuildServiceAgentPoolResource)`
info [Changelog] - Function `BuildServiceAgentPoolClient.UpdatePut` parameter(s) have been changed from `(context.Context, string, string, string, string, BuildServiceAgentPoolSizeProperties)` to `(context.Context, string, string, string, string, BuildServiceAgentPoolResource)`
info [Changelog]
info [Changelog] Total 2 breaking change(s), 0 additive change(s).
️✔️preview/appplatform/mgmt/2021-09-01-preview/appplatform [View full logs]
info [Changelog] ### Features Added
info [Changelog]
info [Changelog] - New const `ActionTypeInternal`
info [Changelog] - New function `PossibleActionTypeValues() []ActionType`
info [Changelog] - New function `OperationDetail.MarshalJSON() ([]byte, error)`
info [Changelog] - New field `ActionType` in struct `OperationDetail`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 4 additive change(s).
️✔️preview/appplatform/mgmt/2021-06-01-preview/appplatform [View full logs]
info [Changelog] ### Features Added
info [Changelog]
info [Changelog] - New const `ActionTypeInternal`
info [Changelog] - New function `OperationDetail.MarshalJSON() ([]byte, error)`
info [Changelog] - New function `PossibleActionTypeValues() []ActionType`
info [Changelog] - New field `SourceMdmNamespace` in struct `MetricSpecification`
info [Changelog] - New field `ActionType` in struct `OperationDetail`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 5 additive change(s).
️✔️preview/appplatform/mgmt/2020-11-01-preview/appplatform [View full logs]
Only show 9 items here, please refer to log for details.
info [Changelog]
info [Changelog] - New const `Internal`
info [Changelog] - New function `OperationDetail.MarshalJSON() ([]byte, error)`
info [Changelog] - New function `PossibleActionTypeValues() []ActionType`
info [Changelog] - New field `SourceMdmNamespace` in struct `MetricSpecification`
info [Changelog] - New field `ToBeExportedForShoebox` in struct `MetricDimension`
info [Changelog] - New field `ActionType` in struct `OperationDetail`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 6 additive change(s).
️✔️preview/appplatform/mgmt/2019-05-01-preview/appplatform [View full logs]
info [Changelog] This is a new package
info [Changelog]
info [Changelog] ### Features Added
info [Changelog]
info [Changelog] - New const `Trace`
info [Changelog] - New function `CreateOrUpdateProperties.MarshalJSON() ([]byte, error)`
info [Changelog] - New function `ResourceSku.MarshalJSON() ([]byte, error)`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 3 additive change(s).
info [Changelog] ### Other Changes
info [Changelog]
info [Changelog] Total 0 breaking change(s), 0 additive change(s).
️✔️preview/signalr/mgmt/2021-09-01-preview/signalr [View full logs]
info [Changelog] This is a new package
info [Changelog]
️✔️preview/signalr/mgmt/2021-06-01-preview/signalr [View full logs]
Only show 9 items here, please refer to log for details.
info [Changelog]
info [Changelog] - New const `TypeMicrosoftSignalRServiceSignalR`
info [Changelog] - New const `NameFreeF1`
info [Changelog] - New const `NameStandardS1`
info [Changelog] - New const `TypeMicrosoftSignalRServicewebPubSub`
info [Changelog] - New function `PossibleTypeValues() []Type`
info [Changelog] - New function `PossibleNameValues() []Name`
info [Changelog]
info [Changelog] Total 2 breaking change(s), 6 additive change(s).
️✔️preview/signalr/mgmt/2021-04-01-preview/signalr [View full logs]
info [Changelog] ### Other Changes
info [Changelog]
info [Changelog] Total 0 breaking change(s), 0 additive change(s).
️✔️preview/signalr/mgmt/2020-07-01-preview/signalr [View full logs]
info [Changelog] ### Features Added
info [Changelog]
info [Changelog] - New function `ResourceSku.MarshalJSON() ([]byte, error)`
info [Changelog]
info [Changelog] Total 0 breaking change(s), 1 additive change(s).
️✔️preview/signalr/mgmt/2018-03-01-preview/signalr [View full logs]
info [Changelog] ### Other Changes
info [Changelog]
info [Changelog] Total 0 breaking change(s), 0 additive change(s).
⚠️Warning [Logs] Generate from 841eea9bc785fe94b6de7b0527d58c5c1ed1cf5b. Schema Automation 14.0.0
command .sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
cmderr [initScript.sh] WARN old lockfile
cmderr [initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm,
cmderr [initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry.
cmderr [initScript.sh] npm WARN old lockfile
cmderr [initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient...
cmderr [initScript.sh] npm WARN old lockfile
warn File azure-resource-manager-schemas_tmp/initOutput.json not found to read
command .sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
Hi @tianxchen-ms, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.
Hi @tianxchen-ms, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. 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. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
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.
-[ ] 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.
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.