azure-rest-api-specs
azure-rest-api-specs copied to clipboard
Dev healthcareapis microsoft.healthcare apis 2022 10 01 preview
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:
- What's the purpose of the update?
- [ ] new service onboarding
- [x] new API version
- [ ] update existing version for new feature
- [ ] update existing version to fix swagger quality issue in s360
- [ ] Other, please clarify
- 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.
- When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
- 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:
- [x] I commit to follow the Breaking Change Policy of "no breaking changes"
- [x] I have reviewed the documentation for the workflow.
- [x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Applicability: :warning:
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:
-
[x] Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
- 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.
Hi, @tongwu-msft Thanks for your PR. I am workflow bot for review process. Here are some small tips.
Swagger Validation Report
️️✔️
BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️
Breaking Change(Cross-Version): 1 Warnings warning [Detail]
compared swaggers (via Oad v0.10.2)] | new version | base version |
---|---|---|
healthcare-apis.json | 2022-10-01-preview(bdf770c) | 2022-06-01(main) |
healthcare-apis.json | 2022-10-01-preview(bdf770c) | 2022-01-31-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
Rule | Message |
---|---|
:warning: 1036 - ConstraintChanged | The new version has a different 'maximum' value than the previous one. New: Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json#L2628:9 Old: Microsoft.HealthcareApis/preview/2022-01-31-preview/healthcare-apis.json#L2363:9 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
LintDiff: 4 Errors, 0 Warnings failed [Detail]
compared tags (via openapi-validator v2.0.0) | new version | base version |
---|---|---|
package-preview-2022-10 | package-preview-2022-10(bdf770c) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
Rule | Message | Related RPC [For API reviewers] |
---|---|---|
ResourceNameRestriction |
The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction. Location: Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json#L2202 |
RPC-V2-URI-5 |
ResourceNameRestriction |
The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction. Location: Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json#L2247 |
RPC-V2-URI-5 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json#L2401 |
RPC-V2-ASYNC-7 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json#L2451 |
RPC-V2-ASYNC-7 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
API Readiness check failed. Please make sure your service is deployed. |
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.HealthcareApis' for api version '2022-10-01-preview'. The supported api-versions are '2018-08-20-preview, 2019-09-16, 2020-03-15, 2020-03-30, 2021-01-11, 2021-06-01-preview, 2021-11-01, 2022-01-31-preview, 2022-05-15, 2022-06-01'." |
️⚠️
~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️
~[Staging] SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
️️✔️
ApiDocPreview succeeded [Detail] [Expand]
Please click here to preview with your @microsoft account.
️️✔️
azure-sdk-for-net-track2 succeeded [Detail] [Expand]
️✔️
Succeeded [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json command pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
️✔️
Azure.ResourceManager.HealthcareApis [View full logs] [Release SDK Changes]info [Changelog]
️⚠️
azure-sdk-for-python-track2 warning [Detail]
⚠️
Warning [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command 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] notice cmderr [automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.1.3 cmderr [automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.3> cmderr [automation_generate.sh] npm notice Run `npm install -g [email protected]` to update! cmderr [automation_generate.sh] npm notice
️✔️
track2_azure-mgmt-healthcareapis [View full logs] [Release SDK Changes]info [Changelog] ### Features Added info [Changelog] info [Changelog] - Added operation group AnalyticsConnectorsOperations
️⚠️
azure-sdk-for-java warning [Detail]
⚠️
Warning [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command ./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json cmderr [init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1 cmderr [init.sh] [notice] To update, run: pip install --upgrade pip cmderr [init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1 cmderr [init.sh] [notice] To update, run: pip install --upgrade pip command ./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
️✔️
azure-resourcemanager-healthcareapis [View full logs] [Release SDK Changes]
️️✔️
azure-sdk-for-go succeeded [Detail] [Expand]
️✔️
Succeeded [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json command generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
️✔️
sdk/resourcemanager/healthcareapis/armhealthcareapis [View full logs] [Release SDK Changes]info [Changelog] ### Features Added info [Changelog] info [Changelog] - New type alias `AnalyticsConnectorDataDestinationType` with values `AnalyticsConnectorDataDestinationTypeDatalake` info [Changelog] - New type alias `AnalyticsConnectorDataSourceType` with values `AnalyticsConnectorDataSourceTypeFhirservice` info [Changelog] - New type alias `AnalyticsConnectorMappingType` with values `AnalyticsConnectorMappingTypeFhirToParquet` info [Changelog] - New type alias `FhirServiceVersion` with values `FhirServiceVersionR4`, `FhirServiceVersionSTU3` info [Changelog] - New function `*AnalyticsConnectorDataDestination.GetAnalyticsConnectorDataDestination() *AnalyticsConnectorDataDestination` info [Changelog] - New function `*AnalyticsConnectorDataLakeDataDestination.GetAnalyticsConnectorDataDestination() *AnalyticsConnectorDataDestination` info [Changelog] - New function `*AnalyticsConnectorDataSource.GetAnalyticsConnectorDataSource() *AnalyticsConnectorDataSource` info [Changelog] - New function `*AnalyticsConnectorFhirServiceDataSource.GetAnalyticsConnectorDataSource() *AnalyticsConnectorDataSource` info [Changelog] - New function `*AnalyticsConnectorFhirToParquetMapping.GetAnalyticsConnectorMapping() *AnalyticsConnectorMapping` info [Changelog] - New function `*AnalyticsConnectorMapping.GetAnalyticsConnectorMapping() *AnalyticsConnectorMapping` info [Changelog] - New function `NewAnalyticsConnectorsClient(string, azcore.TokenCredential, *arm.ClientOptions) (*AnalyticsConnectorsClient, error)` info [Changelog] - New function `*AnalyticsConnectorsClient.BeginCreateOrUpdate(context.Context, string, string, string, AnalyticsConnector, *AnalyticsConnectorsClientBeginCreateOrUpdateOptions) (*runtime.Poller[AnalyticsConnectorsClientCreateOrUpdateResponse], error)` info [Changelog] - New function `*AnalyticsConnectorsClient.BeginDelete(context.Context, string, string, string, *AnalyticsConnectorsClientBeginDeleteOptions) (*runtime.Poller[AnalyticsConnectorsClientDeleteResponse], error)` info [Changelog] - New function `*AnalyticsConnectorsClient.Get(context.Context, string, string, string, *AnalyticsConnectorsClientGetOptions) (AnalyticsConnectorsClientGetResponse, error)` info [Changelog] - New function `*AnalyticsConnectorsClient.NewListByWorkspacePager(string, string, *AnalyticsConnectorsClientListByWorkspaceOptions) *runtime.Pager[AnalyticsConnectorsClientListByWorkspaceResponse]` info [Changelog] - New function `*AnalyticsConnectorsClient.BeginUpdate(context.Context, string, string, string, AnalyticsConnectorPatchResource, *AnalyticsConnectorsClientBeginUpdateOptions) (*runtime.Poller[AnalyticsConnectorsClientUpdateResponse], error)` info [Changelog] - New struct `AnalyticsConnector` info [Changelog] - New struct `AnalyticsConnectorCollection` info [Changelog] - New struct `AnalyticsConnectorDataLakeDataDestination` info [Changelog] - New struct `AnalyticsConnectorFhirServiceDataSource` info [Changelog] - New struct `AnalyticsConnectorFhirToParquetMapping` info [Changelog] - New struct `AnalyticsConnectorPatchResource` info [Changelog] - New struct `AnalyticsConnectorProperties` info [Changelog] - New struct `AnalyticsConnectorsClient` info [Changelog] - New struct `AnalyticsConnectorsClientCreateOrUpdateResponse` info [Changelog] - New struct `AnalyticsConnectorsClientDeleteResponse` info [Changelog] - New struct `AnalyticsConnectorsClientListByWorkspaceResponse` info [Changelog] - New struct `AnalyticsConnectorsClientUpdateResponse` info [Changelog] - New struct `CorsConfiguration` info [Changelog] - New field `CorsConfiguration` in struct `DicomServiceProperties` info [Changelog] - New field `EnableRegionalMdmAccount` in struct `MetricSpecification` info [Changelog] - New field `IsInternal` in struct `MetricSpecification` info [Changelog] - New field `MetricFilterPattern` in struct `MetricSpecification` info [Changelog] - New field `ResourceIDDimensionNameOverride` in struct `MetricSpecification` info [Changelog] - New field `SourceMdmAccount` in struct `MetricSpecification` info [Changelog] info [Changelog] Total 0 breaking change(s), 52 additive change(s).
️️✔️
azure-sdk-for-js succeeded [Detail] [Expand]
️✔️
Succeeded [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json 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
️✔️
@azure/arm-healthcareapis [View full logs] [Release SDK Changes]info [Changelog] **Features** info [Changelog] info [Changelog] - Added operation group AnalyticsConnectors info [Changelog] - Added Interface AnalyticsConnector info [Changelog] - Added Interface AnalyticsConnectorCollection info [Changelog] - Added Interface AnalyticsConnectorDataDestination info [Changelog] - Added Interface AnalyticsConnectorDataLakeDataDestination info [Changelog] - Added Interface AnalyticsConnectorDataSource info [Changelog] - Added Interface AnalyticsConnectorFhirServiceDataSource info [Changelog] - Added Interface AnalyticsConnectorFhirToParquetMapping info [Changelog] - Added Interface AnalyticsConnectorMapping info [Changelog] - Added Interface AnalyticsConnectorPatchResource info [Changelog] - Added Interface AnalyticsConnectorsCreateOrUpdateOptionalParams info [Changelog] - Added Interface AnalyticsConnectorsDeleteOptionalParams info [Changelog] - Added Interface AnalyticsConnectorsGetOptionalParams info [Changelog] - Added Interface AnalyticsConnectorsListByWorkspaceNextOptionalParams info [Changelog] - Added Interface AnalyticsConnectorsListByWorkspaceOptionalParams info [Changelog] - Added Interface AnalyticsConnectorsUpdateOptionalParams info [Changelog] - Added Interface CorsConfiguration info [Changelog] - Added Interface FhirServiceImportConfiguration info [Changelog] - Added Interface ServiceImportConfigurationInfo info [Changelog] - Added Type Alias AnalyticsConnectorDataDestinationType info [Changelog] - Added Type Alias AnalyticsConnectorDataDestinationUnion info [Changelog] - Added Type Alias AnalyticsConnectorDataSourceType info [Changelog] - Added Type Alias AnalyticsConnectorDataSourceUnion info [Changelog] - Added Type Alias AnalyticsConnectorMappingType info [Changelog] - Added Type Alias AnalyticsConnectorMappingUnion info [Changelog] - Added Type Alias AnalyticsConnectorsCreateOrUpdateResponse info [Changelog] - Added Type Alias AnalyticsConnectorsGetResponse info [Changelog] - Added Type Alias AnalyticsConnectorsListByWorkspaceNextResponse info [Changelog] - Added Type Alias AnalyticsConnectorsListByWorkspaceResponse info [Changelog] - Added Type Alias AnalyticsConnectorsUpdateResponse info [Changelog] - Added Type Alias FhirServiceVersion info [Changelog] - Interface DicomService has a new optional parameter corsConfiguration info [Changelog] - Interface FhirService has a new optional parameter importConfiguration info [Changelog] - Interface MetricSpecification has a new optional parameter enableRegionalMdmAccount info [Changelog] - Interface MetricSpecification has a new optional parameter isInternal info [Changelog] - Interface MetricSpecification has a new optional parameter metricFilterPattern info [Changelog] - Interface MetricSpecification has a new optional parameter resourceIdDimensionNameOverride info [Changelog] - Interface MetricSpecification has a new optional parameter sourceMdmAccount info [Changelog] - Interface ServicesProperties has a new optional parameter importConfiguration info [Changelog] - Class HealthcareApisManagementClient has a new parameter analyticsConnectors info [Changelog] - Added Enum KnownAnalyticsConnectorDataDestinationType info [Changelog] - Added Enum KnownAnalyticsConnectorDataSourceType info [Changelog] - Added Enum KnownAnalyticsConnectorMappingType info [Changelog] - Added Enum KnownFhirServiceVersion
️⚠️
azure-resource-manager-schemas warning [Detail]
⚠️
Warning [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. Schema Automation 14.0.0command .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
️✔️
healthcareapis [View full logs] [Release Schema Changes]
️❌
azure-powershell failed [Detail]
❌
Failed [Logs]Release - Generate from 878fe925bc9f48b7b1451be3e6842bf44f938c34. SDK Automation 14.0.0command sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json command pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
❌
Az.healthcareapis [View full logs] [Release SDK Changes]
Hi @tongwu-msft, 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.
Task | How to fix | Priority |
---|---|---|
Avocado | Fix-Avocado | High |
Semantic validation | Fix-SemanticValidation-Error | High |
Model validation | Fix-ModelValidation-Error | High |
LintDiff | Fix-LintDiff | high |
Hi, @tongwu-msft your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]).
},
Use 201/200 + provisioning state instead of 202, see : https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#creatingupdating-using-put
Refers to: specification/healthcareapis/resource-manager/Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json:2347 in b3f0ba4. [](commit_id = b3f0ba445450b159721ba80b6bfb884c1d5c5ae6, deletion_comment = False)
},
Is 200 needed here? See https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#updating-using-patch
Refers to: specification/healthcareapis/resource-manager/Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json:2406 in b3f0ba4. [](commit_id = b3f0ba445450b159721ba80b6bfb884c1d5c5ae6, deletion_comment = False)
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove ARMChangesRequested
},
Is 200 needed here? See https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#updating-using-patch
Refers to: specification/healthcareapis/resource-manager/Microsoft.HealthcareApis/preview/2022-10-01-preview/healthcare-apis.json:2406 in b3f0ba4. [](commit_id = b3f0ba4, deletion_comment = False)
Thanks @zizw123, we verified currently we rely on the RP SDK logic for the return value 200 (Microsoft.Azure.ResourceProvider.Routing 6.0.1934.71), it would return 200 for patch operation with async uri.
Generated ApiView
Language | Package Name | ApiView Link |
---|---|---|
Go | sdk/resourcemanager/healthcareapis/armhealthcareapis | Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI. |
Python | track2_azure-mgmt-healthcareapis | Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI. |
Java | azure-resourcemanager-healthcareapis | Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI. |
.Net | Azure.ResourceManager.HealthcareApis | Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI. |
JavaScript | @azure/arm-healthcareapis | Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI. |
Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment.
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
Looks good
Hi, @tongwu-msft. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity
label.
Hi, @tongwu-msft. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity
label.
Hi, @tongwu-msft. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee.
Hi, @tongwu-msft. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity
label.
Hi, @tongwu-msft. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee.
Hi @tongwu-msft, 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. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.