mgmt release planner test #22119

dw511214992 · 2023-01-10T03:28:40Z

ARM API Information (Control Plane)

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

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.

Changelog

Add a changelog entry for this PR by answering the following questions:

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
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.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

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?

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 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.

NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)

Please follow the link to find more details on PR review process.

openapi-workflow-bot · 2023-01-10T03:28:43Z

Hi, @dw511214992 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-pipeline-app · 2023-01-10T03:28:43Z

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

compared swaggers (via Oad v0.10.4)]	new version	base version
databoxedge.json	2022-03-01(7931313)	2022-03-01(main)

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️⚠️LintDiff: 0 Warnings warning [Detail]

compared tags (via openapi-validator v2.0.0)	new version	base version
package-2022-03-01	package-2022-03-01(7931313)	package-2022-03-01(main)

The following errors/warnings exist before current PR submission:

Only 30 items are listed, please refer to log for more details.

Rule	Message
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L188
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L189
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L236
`❌` DeleteOperationAsyncResponseValidation	An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L292
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L292
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L320
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L340
`❌` PatchSkuProperty	The patch operation body parameter schema should contains property 'sku'. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L354
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L394
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L395
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L443
`❌` ParametersOrder	The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L444
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L496
`❌` ParametersOrder	The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L497
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L545
`❌` ParametersOrder	The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L546
`❌` CreateOperationAsyncResponseValidation	An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L597
`❌` ParametersOrder	The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L597
`❌` CreateOperationAsyncResponseValidation	An async PUT operation must return 201. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L637
`❌` CreateOperationAsyncResponseValidation	Only 201 is the supported response code for PUT async response. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L644
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L644
`❌` DeleteOperationAsyncResponseValidation	An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L661
`❌` ParametersOrder	The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L661
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L696
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L717
`❌` PostOperationAsyncResponseValidation	An async POST operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L718
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L759
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L783
`❌` OperationIdNounVerb	Per the Noun_Verb convention for Operation Ids, the noun 'DeviceCapacityInfo' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L789
`❌` ResourceNameRestriction	The resource name parameter 'deviceName' should be defined with a 'pattern' restriction. Location: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L829

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️ApiReadinessCheck succeeded [Detail] [Expand]

️⚠️~[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]

️️✔️~[Staging] CadlAPIView succeeded [Detail] [Expand]

️❌ModelValidation: 27 Errors, 0 Warnings failed [Detail]

Rule	Message
`❌` MISSING_RESOURCE_ID	id is required to return in response of GET/PUT resource calls but not being provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L5103:26 ExampleUrl: stable/2022-03-01/examples/DataBoxEdgeDevicePut.json#L30:15
`❌` MISSING_RESOURCE_ID	id is required to return in response of GET/PUT resource calls but not being provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L5103:26 ExampleUrl: stable/2022-03-01/examples/DataBoxEdgeDevicePutWithDataResidency.json#L35:15
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L316:22 ExampleUrl: stable/2022-03-01/examples/DataBoxEdgeDeviceDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L692:22 ExampleUrl: stable/2022-03-01/examples/BandwidthScheduleDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L758:22 ExampleUrl: stable/2022-03-01/examples/DeviceCapacityRequestPost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L1060:22 ExampleUrl: stable/2022-03-01/examples/DownloadUpdatesPost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L1199:22 ExampleUrl: stable/2022-03-01/examples/InstallUpdatesPost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L1597:22 ExampleUrl: stable/2022-03-01/examples/OrderDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L1864:22 ExampleUrl: stable/2022-03-01/examples/RoleDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2113:22 ExampleUrl: stable/2022-03-01/examples/DeleteAddons.json
`❌` MISSING_RESOURCE_ID	id is required to return in response of GET/PUT resource calls but not being provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L7311:38 ExampleUrl: stable/2022-03-01/examples/ListMonitoringConfig.json#L16:11
`❌` MISSING_RESOURCE_ID	id is required to return in response of GET/PUT resource calls but not being provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L7311:38 ExampleUrl: stable/2022-03-01/examples/GetMonitoringConfig.json#L14:15
`❌` MISSING_RESOURCE_ID	id is required to return in response of GET/PUT resource calls but not being provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L7311:38 ExampleUrl: stable/2022-03-01/examples/PutMonitoringConfig.json#L34:15
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2341:22 ExampleUrl: stable/2022-03-01/examples/DeleteMonitoringConfig.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2391:22 ExampleUrl: stable/2022-03-01/examples/ScanForUpdatesPost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2447:22 ExampleUrl: stable/2022-03-01/examples/SecuritySettingsUpdatePost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2665:22 ExampleUrl: stable/2022-03-01/examples/ShareDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2722:22 ExampleUrl: stable/2022-03-01/examples/ShareRefreshPost.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L2940:22 ExampleUrl: stable/2022-03-01/examples/SACDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3161:22 ExampleUrl: stable/2022-03-01/examples/StorageAccountDelete.json
`❌` INVALID_REQUEST_PARAMETER	api-version 2021-06-01 is not equal to swagger version Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3240:14 ExampleUrl: stable/2022-03-01/examples/ContainerGet.json#L2:17
`❌` INVALID_REQUEST_PARAMETER	api-version 2021-06-01 is not equal to swagger version Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3298:14 ExampleUrl: stable/2022-03-01/examples/ContainerPut.json#L2:17
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3407:22 ExampleUrl: stable/2022-03-01/examples/ContainerDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3468:22 ExampleUrl: stable/2022-03-01/examples/ContainerRefresh.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3693:22 ExampleUrl: stable/2022-03-01/examples/TriggerDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L3752:22 ExampleUrl: stable/2022-03-01/examples/TriggerSupportPackage.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.DataBoxEdge/stable/2022-03-01/databoxedge.json#L4133:22 ExampleUrl: stable/2022-03-01/examples/UserDelete.json

️️✔️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.

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2023-01-10T03:28:44Z

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

 Please click here to preview with your @microsoft account.

️❌SDK Breaking Change Tracking failed [Detail]

Breaking Changes Tracking

❌azure-sdk-for-go - sdk/resourcemanager/databoxedge/armdataboxedge - Approved - 2.0.0

+	Struct `CloudErrorBody` has been removed
+	Struct `CloudError` has been removed

❌azure-sdk-for-js - @azure/arm-databoxedge - Approved - 3.0.0

+	Interface DevicesListByResourceGroupNextOptionalParams no longer has parameter expand
+	Interface DevicesListBySubscriptionNextOptionalParams no longer has parameter expand
+	Interface TriggersListByDataBoxEdgeDeviceNextOptionalParams no longer has parameter filter
+	Interface UsersListByDataBoxEdgeDeviceNextOptionalParams no longer has parameter filter

️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]

️✔️Succeeded [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. SDK Automation 14.0.0

command	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.DataBoxEdge [View full logs] [Preview SDK Changes]
- Azure.ResourceManager.DataBoxEdge.1.1.0-alpha.20230119.1.nupkg
```
info	[Changelog]
```

️⚠️ azure-sdk-for-python-track2 warning [Detail]

⚠️Warning [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. 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]
cmderr	[automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.3.1
cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.3.1>
cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
cmderr	[automation_generate.sh] npm notice

️✔️track2_azure-mgmt-databoxedge [View full logs] [Preview SDK Changes]

info	[Changelog] ### Features Added
info	[Changelog]
info	[Changelog]   - Added operation group DiagnosticSettingsOperations
info	[Changelog]   - Added operation group SupportPackagesOperations
info	[Changelog]   - Model DataBoxEdgeSku has a new parameter capabilities

️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

️✔️Succeeded [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. 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
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-databoxedge [View full logs] [Preview SDK Changes] Breaking Change Detected

azure-arm-databoxedge-3.0.0.tgz

info	[Changelog] **Features**
info	[Changelog]
info	[Changelog]   - Added operation group DeviceCapacityCheck
info	[Changelog]   - Added operation group DeviceCapacityInfoOperations
info	[Changelog]   - Added Interface ClusterCapacityViewData
info	[Changelog]   - Added Interface ClusterGpuCapacity
info	[Changelog]   - Added Interface ClusterMemoryCapacity
info	[Changelog]   - Added Interface ClusterStorageViewData
info	[Changelog]   - Added Interface DeviceCapacityCheckCheckResourceCreationFeasibilityOptionalParams
info	[Changelog]   - Added Interface DeviceCapacityInfo
info	[Changelog]   - Added Interface DeviceCapacityInfoGetDeviceCapacityInfoOptionalParams
info	[Changelog]   - Added Interface DeviceCapacityRequestInfo
info	[Changelog]   - Added Interface HostCapacity
info	[Changelog]   - Added Interface NumaNodeData
info	[Changelog]   - Added Interface VmMemory
info	[Changelog]   - Added Interface VmPlacementRequestResult
info	[Changelog]   - Added Type Alias ClusterWitnessType
info	[Changelog]   - Added Type Alias DeviceCapacityInfoGetDeviceCapacityInfoResponse
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter cloudWitnessContainerName
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter cloudWitnessStorageAccountName
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter cloudWitnessStorageEndpoint
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter clusterWitnessType
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter fileShareWitnessLocation
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter fileShareWitnessUsername
info	[Changelog]   - Interface DataBoxEdgeDeviceExtendedInfo has a new optional parameter systemData
info	[Changelog]   - Interface Order has a new optional parameter kind
info	[Changelog]   - Interface Order has a new optional parameter orderId
info	[Changelog]   - Added Enum KnownClusterWitnessType
info	[Changelog]   - Enum KnownSkuName has a new value EdgeMRTCP
info	[Changelog]   - Enum KnownSkuName has a new value EP2128GPU1Mx1W
info	[Changelog]   - Enum KnownSkuName has a new value EP2256GPU2Mx1
info	[Changelog]   - Enum KnownSkuName has a new value EP264Mx1W
info	[Changelog]
info	[Changelog] **Breaking Changes**
info	[Changelog]
info	[Changelog]   - Interface DevicesListByResourceGroupNextOptionalParams no longer has parameter expand
info	[Changelog]   - Interface DevicesListBySubscriptionNextOptionalParams no longer has parameter expand
info	[Changelog]   - Interface TriggersListByDataBoxEdgeDeviceNextOptionalParams no longer has parameter filter
info	[Changelog]   - Interface UsersListByDataBoxEdgeDeviceNextOptionalParams no longer has parameter filter

️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

️✔️Succeeded [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. SDK Automation 14.0.0

command	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/databoxedge/armdataboxedge [View full logs] [Preview SDK Changes] Breaking Change Detected

info	[Changelog] ### Breaking Changes
info	[Changelog]
info	[Changelog] - Struct `CloudError` has been removed
info	[Changelog] - Struct `CloudErrorBody` has been removed
info	[Changelog]
info	[Changelog] Total 4 breaking change(s), 0 additive change(s).

️⚠️ azure-sdk-for-java warning [Detail]

⚠️Warning [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. SDK Automation 14.0.0

command	./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-databoxedge [View full logs] [Preview SDK Changes]

️⚠️ azure-resource-manager-schemas warning [Detail]

⚠️Warning [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. 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
warn	No file changes detected after generation

️✔️databoxedge [View full logs]

️️✔️ azure-powershell succeeded [Detail] [Expand]

️✔️Succeeded [Logs] Generate from de00d8d3df35cc2990cbbd7c223e66db27892285. SDK Automation 14.0.0

command	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.DataBoxEdge [View full logs] [Preview SDK Changes]
- Az.DataBoxEdge.0.1.0.nupkg

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2023-01-10T03:28:45Z

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/databoxedge/armdataboxedge	https://apiview.dev/Assemblies/Review/deb45a2f11c94fa6b193a5bf282ea3aa
Java	azure-resourcemanager-databoxedge	https://apiview.dev/Assemblies/Review/460ddf34cfae4f87b23728080203bf9e
.Net	Azure.ResourceManager.DataBoxEdge	There is no API change compared with the previous version
JavaScript	@azure/arm-databoxedge	https://apiview.dev/Assemblies/Review/f4eaa9611514403cb87421cf1fd3cc8e

live1206 · 2023-01-10T06:55:09Z

suppress model validation

live1206 · 2023-01-12T00:13:47Z

Suppression for model validation

fengzhou-msft · 2023-01-12T06:33:23Z

test

live1206 · 2023-01-19T01:41:15Z

/azp run

azure-pipelines · 2023-01-19T01:41:25Z

Azure Pipelines successfully started running 1 pipeline(s).

Update readme.md

5ff5ef4

azure-sdk mentioned this pull request Jan 10, 2023

[AutoPR sdk/resourcemanager/databoxedge/armdataboxedge] mgmt release planner test azure-sdk/azure-sdk-for-go#3977

Closed

openapi-pipeline-app bot added the CI-BreakingChange-Go label Jan 10, 2023

AzureRestAPISpecReview added the resource-manager label Jan 10, 2023

openapi-pipeline-app bot added the CI-BreakingChange-JavaScript label Jan 10, 2023

zzvswxy added the Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates label Jan 10, 2023

azure-sdk mentioned this pull request Jan 10, 2023

[AutoPR-databoxedge]mgmt release planner test Azure/azure-sdk-for-net#33378

Closed

zzvswxy added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Jan 10, 2023

dw511214992 added Approved-SdkBreakingChange-Go Approve the breaking change tracking for azure-sdk-for-go Approved-SdkBreakingChange-JavaScript and removed ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Jan 10, 2023

Update databoxedge.json

7931313

openapi-workflow-bot bot added commitAfterSignedOff and removed Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates labels Jan 10, 2023

zzvswxy added the Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates label Jan 10, 2023

live1206 added new-rp-namespace and removed new-rp-namespace labels Jan 11, 2023

azure-sdk mentioned this pull request Jan 11, 2023

[AutoPR-databoxedge]mgmt release planner test openapi-env-test/azure-sdk-for-net#1442

Closed

azure-sdk mentioned this pull request Jan 12, 2023

[AutoPR-databoxedge]mgmt release planner test openapi-env-test/azure-sdk-for-net#1446

Closed

leniatgh added Approved-ModelValidation and removed Approved-ModelValidation labels Jan 12, 2023

live1206 added the new-rp-namespace label Jan 13, 2023

dw511214992 added Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates and removed Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates labels Jan 16, 2023

dw511214992 closed this Jan 16, 2023

dw511214992 reopened this Jan 16, 2023

azure-sdk mentioned this pull request Jan 18, 2023

[AutoPR-databoxedge]test release planner app Azure/azure-sdk-for-net#33568

Closed

live1206 removed the new-rp-namespace label Jan 19, 2023

azure-sdk mentioned this pull request Jan 31, 2023

[AutoPR-databoxedge]test release planner app openapi-env-test/azure-sdk-for-js#1869

Closed

live1206 added the APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. label Feb 10, 2023

ladonnaq added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Jun 20, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

mgmt release planner test #22119

mgmt release planner test #22119

dw511214992 commented Jan 10, 2023 •

edited by openapi-workflow-bot bot

Loading

openapi-workflow-bot bot commented Jan 10, 2023

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading

Breaking Changes Tracking

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading

live1206 commented Jan 10, 2023

live1206 commented Jan 12, 2023

fengzhou-msft commented Jan 12, 2023

live1206 commented Jan 19, 2023

azure-pipelines bot commented Jan 19, 2023

mgmt release planner test #22119

Are you sure you want to change the base?

mgmt release planner test #22119

Conversation

dw511214992 commented Jan 10, 2023 • edited by openapi-workflow-bot bot Loading

ARM API Information (Control Plane)

Changelog

Contribution checklist (MS Employees Only):

ARM API Review Checklist

Breaking Change Review Checklist

openapi-workflow-bot bot commented Jan 10, 2023

openapi-pipeline-app bot commented Jan 10, 2023 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Jan 10, 2023 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-pipeline-app bot commented Jan 10, 2023 • edited Loading

Generated ApiView

live1206 commented Jan 10, 2023

live1206 commented Jan 12, 2023

fengzhou-msft commented Jan 12, 2023

live1206 commented Jan 19, 2023

azure-pipelines bot commented Jan 19, 2023

dw511214992 commented Jan 10, 2023 •

edited by openapi-workflow-bot bot

Loading

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 10, 2023 •

edited

Loading