Updating specs for PAN #23435

Vibhuti-Sharma-Microsoft · 2023-04-05T06:41:54Z

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. April
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-04-05T06:41:57Z

Hi, @Vibhuti-Sharma-Microsoft 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. vscswagger@microsoft.com

openapi-pipeline-app · 2023-04-05T06:41:58Z

Swagger Validation Report

️❌BreakingChange: 2 Errors, 0 Warnings failed [Detail]

compared swaggers (via Oad v0.10.4)]	new version	base version
PaloAltoNetworks.Cloudngfw.json	2022-08-29-preview(c922325)	2022-08-29-preview(main)

Rule	Message
`❌` 1038 - AddedPath	The new version is adding a path that was not found in the old version. New: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L2563:5
`❌` 1038 - AddedPath	The new version is adding a path that was not found in the old version. New: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L2611:5

️️✔️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-08-29-preview	package-2022-08-29-preview(c922325)	package-2022-08-29-preview(main)

The following errors/warnings exist before current PR submission:

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

Rule	Message
`❌` OperationIdNounVerb	Per the Noun_Verb convention for Operation Ids, the noun 'LocalRules' 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: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L3865
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L777
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L783
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L790
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L830
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L843
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L849
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L855
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L861
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L894
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L907
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L913
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L946
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L985
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L998
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1004
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1050
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1056
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1063
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1313
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1361
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1406
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1834
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1882
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L1927
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L2533
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L3501
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L3507
⚠️ ParameterDescription	Parameter should have a description. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L3514
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: PaloAltoNetworks.Cloudngfw/preview/2022-08-29-preview/PaloAltoNetworks.Cloudngfw.json#L3554

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

️️✔️SwaggerAPIView succeeded [Detail] [Expand]

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

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

️️✔️TypeSpec Validation succeeded [Detail] [Expand]

Validation passes for TypeSpec Validation.

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

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

openapi-pipeline-app · 2023-04-05T06:41:58Z

Swagger Generation Artifacts

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

 Please click here to preview with your @microsoft account.

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

Breaking Changes Tracking

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

⚠️Warning [Logs]Release - Generate from cb593f0. 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 minor version of npm available! 9.5.0 -> 9.6.4
cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.4>
cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.6.4` to update!
cmderr	[automation_generate.sh] npm notice

️✔️track2_azure-mgmt-paloaltonetworksngfw [View full logs] [Release SDK Changes]
- azure-mgmt-paloaltonetworksngfw-1.0.0b1.zip
- azure_mgmt_paloaltonetworksngfw-1.0.0b1-py3-none-any.whl
```
info	[Changelog]   - Initial Release
```

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

️✔️Succeeded [Logs]Release - Generate from cb593f0. 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
command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json

️✔️azure-resourcemanager-paloaltonetworks [View full logs] [Release SDK Changes]

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

️✔️Succeeded [Logs]Release - Generate from cb593f0. 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/paloaltonetworksngfw/armpanngfw [View full logs] [Release SDK Changes]
```
info	[Changelog] This is a new package
info	[Changelog]
```

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

️✔️Succeeded [Logs]Release - Generate from cb593f0. 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-paloaltonetworksngfw [View full logs] [Release SDK Changes]
- azure-arm-paloaltonetworksngfw-1.0.0-beta.1.tgz
```
info	[Changelog]
error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
```

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

⚠️Warning [Logs]Release - Generate from cb593f0. 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]  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

️✔️paloaltonetworks [View full logs]

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

openapi-workflow-bot · 2023-04-05T06:41:59Z

Hi, @Vibhuti-Sharma-Microsoft your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com).

openapi-pipeline-app · 2023-04-05T06:41:59Z

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/paloaltonetworksngfw/armpanngfw	https://apiview.dev/Assemblies/Review/385bc8b8a30b41cd8f8dcfa81ef66666
Java	azure-resourcemanager-paloaltonetworks	https://apiview.dev/Assemblies/Review/5d141d0f8e204fe4bcf47acfcadf306d
JavaScript	@azure/arm-paloaltonetworksngfw	https://apiview.dev/Assemblies/Review/2d013fbbf37c4da39134b646292ff6e1

Vibhuti-Sharma-Microsoft · 2023-04-05T06:44:15Z

Arm Review for these changes is already complete, as these have been merged to RPSaaSMaster of private repo (azure-rest-api-specs-pr)

openapi-workflow-bot · 2023-04-05T06:49:44Z

NewApiVersionRequired reason:

A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

Vibhuti-Sharma-Microsoft · 2023-04-06T07:11:56Z

NewApiVersionRequired reason: A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support. EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

We are adding changes to the existing api-version as our service is still in private preview. Hence, new api version is not required. These changes are already approved in private repo as well -

Vibhuti-Sharma-Microsoft · 2023-04-06T07:13:23Z

Please provide waiver for Breaking Changes. We are adding changes to the existing api-version as our service is still in private preview. Hence, new api version is not required. These changes are already approved in private repo as well -

https://github.com/Azure/azure-rest-api-specs-pr/pull/11696
https://github.com/Azure/azure-rest-api-specs-pr/pull/11240

openapi-workflow-bot · 2023-04-06T07:35:53Z

Hi @Vibhuti-Sharma-Microsoft, 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.

msyyc · 2023-04-06T07:38:50Z

Hi @mikekistler Considering #23435 (comment), could you help add label to approve for swagger breaking? It blocks the PR merge and I don't have access to add Approved-Breakingchange label.

updated specs

c922325

openapi-assignment-bot bot assigned msyyc Apr 5, 2023

openapi-workflow-bot bot added ARMReview WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 5, 2023

azure-sdk mentioned this pull request Apr 5, 2023

[AutoPR sdk/resourcemanager/paloaltonetworksngfw/armpanngfw] Updating specs for PAN azure-sdk/azure-sdk-for-go#5198

Closed

AzureRestAPISpecReview added NewApiVersionRequired ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager RPaaS labels Apr 5, 2023

Vibhuti-Sharma-Microsoft removed the NewApiVersionRequired label Apr 6, 2023

msyyc added the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label Apr 6, 2023

mikekistler added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Apr 6, 2023

msyyc approved these changes Apr 10, 2023

View reviewed changes

msyyc merged commit cb593f0 into main Apr 10, 2023

msyyc deleted the users/Vibhuti/updatePanSpecs branch April 10, 2023 04:11

azure-sdk mentioned this pull request Apr 10, 2023

[ReleasePR sdk/resourcemanager/paloaltonetworksngfw/armpanngfw] Updating readme to stable version Azure/azure-sdk-for-go#20436

Closed

ladonnaq mentioned this pull request Apr 12, 2023

API Readiness errors and questions for management plane Azure/azure-sdk-tools#5964

Closed

5 tasks

Vibhuti-Sharma-Microsoft mentioned this pull request Apr 13, 2023

Updating .NET SDK for Paloaltonetworks Azure/azure-sdk-for-net#35541

Closed

JoshLove-msft pushed a commit to JoshLove-msft/azure-rest-api-specs that referenced this pull request Apr 25, 2023

updated specs (Azure#23435)

50e339c

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updating specs for PAN #23435

Updating specs for PAN #23435

Vibhuti-Sharma-Microsoft commented Apr 5, 2023 •

edited

Loading

openapi-workflow-bot bot commented Apr 5, 2023

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

Breaking Changes Tracking

openapi-workflow-bot bot commented Apr 5, 2023

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

Vibhuti-Sharma-Microsoft commented Apr 5, 2023

openapi-workflow-bot bot commented Apr 5, 2023

Vibhuti-Sharma-Microsoft commented Apr 6, 2023

Vibhuti-Sharma-Microsoft commented Apr 6, 2023 •

edited

Loading

openapi-workflow-bot bot commented Apr 6, 2023

msyyc commented Apr 6, 2023

Updating specs for PAN #23435

Updating specs for PAN #23435

Conversation

Vibhuti-Sharma-Microsoft commented Apr 5, 2023 • edited 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 Apr 5, 2023

openapi-pipeline-app bot commented Apr 5, 2023 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Apr 5, 2023 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-workflow-bot bot commented Apr 5, 2023

openapi-pipeline-app bot commented Apr 5, 2023 • edited Loading

Generated ApiView

Vibhuti-Sharma-Microsoft commented Apr 5, 2023

openapi-workflow-bot bot commented Apr 5, 2023

Vibhuti-Sharma-Microsoft commented Apr 6, 2023

Vibhuti-Sharma-Microsoft commented Apr 6, 2023 • edited Loading

openapi-workflow-bot bot commented Apr 6, 2023

msyyc commented Apr 6, 2023

Vibhuti-Sharma-Microsoft commented Apr 5, 2023 •

edited

Loading

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

openapi-pipeline-app bot commented Apr 5, 2023 •

edited

Loading

Vibhuti-Sharma-Microsoft commented Apr 6, 2023 •

edited

Loading