Add x-ms-pageable to generate API's that support using nextlink to return resources #26369

mwesigwaguma · 2023-10-25T09:41:31Z

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])

If you need further help with anything, see Getting help section below.

Purpose of this PR

What's the purpose of this PR? Check all that apply. This is mandatory!

New API version. (Such PR should have been generated with OpenAPI Hub).
Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
Update existing version to fix swagger quality issues in S360.
Other, please clarify:
- edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:
- The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
- You believe there is no need for you to request breaking change approval, for any reason.
  Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

openapi-pipeline-app · 2023-10-25T09:41:35Z

Next Steps to Merge

✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM).

openapi-pipeline-app · 2023-10-25T09:41:37Z

Swagger Validation Report

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

There are no breaking changes.

compared swaggers (via Oad v0.10.4)]	new version	base version
application.json	2021-06-01(972c19d)	2021-06-01(main)
cluster.json	2021-06-01(972c19d)	2021-06-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.1.6)	new version	base version
package-2021-06	package-2021-06(972c19d)	package-2021-06(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 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L37
`❌` ResourceNameRestriction	The resource name parameter 'applicationTypeName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L37
`❌` PutResponseCodes	Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L82
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L167
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L176
`❌` ResourceNameRestriction	The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L182
`❌` ResourceNameRestriction	The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L228
`❌` ResourceNameRestriction	The resource name parameter 'applicationTypeName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L228
`❌` ProvisioningStateSpecifiedForLROPut	200 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L276
`❌` ProvisioningStateSpecifiedForLROPut	201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L276
`❌` PutResponseCodes	Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L276
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L320
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L329
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L368
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L377
`❌` ResourceNameRestriction	The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L383
`❌` ResourceNameRestriction	The resource name parameter 'applicationTypeName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L383
`❌` ResourceNameRestriction	The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L432
`❌` ResourceNameRestriction	The resource name parameter 'applicationName' should be defined with a 'pattern' restriction. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L432
`❌` ProvisioningStateSpecifiedForLROPut	200 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L477
`❌` ProvisioningStateSpecifiedForLROPut	201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L477
`❌` PutResponseCodes	Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L477
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L524
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L533
`❌` PatchResponseCodes	Long-running PATCH operations must have responses with 200, 202 and default return codes. They also must not have other response codes. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L538
`❌` PatchIdentityProperty	The patch operation body parameter schema should contain property 'identity'. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L561
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L579
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L588
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L624
`❌` LroErrorContent	Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.ServiceFabric/stable/2021-06-01/application.json#L633

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

Validation passes for Avocado.

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

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

Validation passes for Summary.

️️✔️Automated merging requirements met succeeded [Detail] [Expand]

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

openapi-pipeline-app · 2023-10-25T09:41:38Z

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/servicefabric/armservicefabric - Approved - 2.0.0

+	Operation `*ApplicationTypeVersionsClient.List` has supported pagination, use `*ApplicationTypeVersionsClient.NewListPager` instead.
+	Operation `*ApplicationTypesClient.List` has supported pagination, use `*ApplicationTypesClient.NewListPager` instead.
+	Operation `*ApplicationsClient.List` has supported pagination, use `*ApplicationsClient.NewListPager` instead.
+	Operation `*ClustersClient.ListByResourceGroup` has supported pagination, use `*ClustersClient.NewListByResourceGroupPager` instead.
+	Operation `*ClustersClient.List` has supported pagination, use `*ClustersClient.NewListPager` instead.
+	Operation `*ServicesClient.List` has supported pagination, use `*ServicesClient.NewListPager` instead.

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

️✔️Succeeded [Logs]Release - Generate from 6963bf0. 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.ServiceFabric [View full logs] [Release SDK Changes]
- Azure.ResourceManager.ServiceFabric.1.1.0-alpha.20231101.1.nupkg
```
info	[Changelog]
```

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

⚠️Warning [Logs]Release - Generate from 6963bf0. 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: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
cmderr	[automation_init.sh] WARNING: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
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

️✔️track2_azure-mgmt-servicefabric [View full logs] [Release SDK Changes]
- azure_mgmt_servicefabric-1.0.0b1-py3-none-any.whl
- azure-mgmt-servicefabric-1.0.0b1.zip
```
info	[Changelog] ### Features Added
info	[Changelog]
info	[Changelog]   - Added model ClusterVersionsEnvironment
```

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

⚠️Warning [Logs]Release - Generate from 6963bf0. 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 is available: 23.0.1 -> 23.3.1
cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
cmderr	[init.sh] [notice] A new release of pip is available: 23.0.1 -> 23.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-servicefabric [View full logs] [Release SDK Changes]

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

️✔️Succeeded [Logs]Release - Generate from 6963bf0. 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/servicefabric/armservicefabric [View full logs] [Release SDK Changes] Breaking Change Detected

info	[Changelog] ### Breaking Changes
info	[Changelog]
info	[Changelog] - Operation `*ApplicationTypeVersionsClient.List` has supported pagination, use `*ApplicationTypeVersionsClient.NewListPager` instead.
info	[Changelog] - Operation `*ApplicationTypesClient.List` has supported pagination, use `*ApplicationTypesClient.NewListPager` instead.
info	[Changelog] - Operation `*ApplicationsClient.List` has supported pagination, use `*ApplicationsClient.NewListPager` instead.
info	[Changelog] - Operation `*ClustersClient.List` has supported pagination, use `*ClustersClient.NewListPager` instead.
info	[Changelog] - Operation `*ClustersClient.ListByResourceGroup` has supported pagination, use `*ClustersClient.NewListByResourceGroupPager` instead.
info	[Changelog] - Operation `*ServicesClient.List` has supported pagination, use `*ServicesClient.NewListPager` instead.
info	[Changelog]
info	[Changelog] Total 6 breaking change(s), 0 additive change(s).

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

⚠️Warning [Logs]Release - Generate from 6963bf0. 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]
cmderr	[initScript.sh] npm notice New major version of npm available! 8.19.4 -> 10.2.2
cmderr	[initScript.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.2>
cmderr	[initScript.sh] npm notice Run `npm install -g [email protected]` to update!
cmderr	[initScript.sh] npm notice
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

️✔️servicefabric [View full logs] [Release Schema Changes]

️❌ azure-powershell failed [Detail]

❌Pipeline Framework Failed [Logs]Release - Generate from 6963bf0. 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
SSL error: syscall failure: Broken pipe
Error: SSL error: syscall failure: Broken pipe

⚠️Az.servicefabric.DefaultTag [View full logs]

error	Fatal error: SSL error: syscall failure: Broken pipe
error	The following packages are still pending:
error		Az.servicefabric.DefaultTag

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

openapi-pipeline-app · 2023-10-25T09:41:39Z

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/servicefabric/armservicefabric	https://apiview.dev/Assemblies/Review/0742443e04cb4f688711e91d4706a5c1
.Net	Azure.ResourceManager.ServiceFabric	There is no API change compared with the previous version
Java	azure-resourcemanager-servicefabric	https://apiview.dev/Assemblies/Review/8d54aa5f915a4249b97d7c157be6ee3c

…into update_metadata_with_nextlink

mwesigwaguma · 2023-10-27T17:14:04Z

Hey @ms-henglu, the pipelines are failing because it's missing a tag what needs to be done.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3198200&view=logs&j=8208ad73-bbfb-535f-1f7a-eacbc2e01c49&t=d5c47bea-997c-50f2-3cae-e386acae4653

mwesigwaguma · 2023-11-01T18:23:53Z

/pr RequestMerge

openapi-pipeline-app · 2023-11-01T19:55:58Z

Swagger pipeline restarted successfully, please wait for status update in this comment.

…turn resources (#26369) * update metadata with nextlink * adding missing property to applicationTypeResourceList schema * adding missing property to applicationTypeResourceList schema

update metadata with nextlink

173e471

mwesigwaguma requested a review from samedder as a code owner October 25, 2023 09:41

openapi-assignment-bot bot assigned rkmanda Oct 25, 2023

azure-sdk mentioned this pull request Oct 25, 2023

[AutoPR sdk/resourcemanager/servicefabric/armservicefabric] Add x-ms-pageable to generate API's that support using nextlink to return resources azure-sdk/azure-sdk-for-go#7819

Closed

openapi-pipeline-app bot added the CI-BreakingChange-Go label Oct 25, 2023

azure-sdk mentioned this pull request Oct 25, 2023

[AutoPR servicefabric] Add x-ms-pageable to generate API's that support using nextlink to return resources azure-sdk/azure-resource-manager-schemas#3492

Closed

AzureRestAPISpecReview added ARMReview resource-manager WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Oct 25, 2023

azure-sdk mentioned this pull request Oct 25, 2023

[AutoPR Azure.ResourceManager.ServiceFabric] Add x-ms-pageable to generate API's that support using nextlink to return resources azure-sdk/azure-sdk-for-net#5797

Closed

adding missing property to applicationTypeResourceList schema

7e3f6b6

azure-sdk mentioned this pull request Oct 25, 2023

[AutoPR azure-resourcemanager-servicefabric] Add x-ms-pageable to generate API's that support using nextlink to return resources azure-sdk/azure-sdk-for-java#7805

Closed

adding missing property to applicationTypeResourceList schema

e9cf763

AzureRestAPISpecReview added the ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test label Oct 25, 2023

azure-sdk mentioned this pull request Oct 25, 2023

[AutoPR track2_azure-mgmt-servicefabric] Add x-ms-pageable to generate API's that support using nextlink to return resources azure-sdk/azure-sdk-for-python#5084

Closed

Merge branch 'main' of https://github.com/Azure/azure-rest-api-specs …

972c19d

…into update_metadata_with_nextlink

ms-henglu added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Oct 25, 2023

openapi-workflow-bot bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Oct 25, 2023

raych1 added the Approved-SdkBreakingChange-Go Approve the breaking change tracking for azure-sdk-for-go label Nov 1, 2023

a-santamaria approved these changes Nov 1, 2023

View reviewed changes

github-actions bot added the MergeRequested label Nov 1, 2023

rkmanda approved these changes Nov 1, 2023

View reviewed changes

rkmanda merged commit 6963bf0 into Azure:main Nov 1, 2023

mwesigwaguma mentioned this pull request Nov 14, 2023

Updating Service Fabric commands to use updated APIs Azure/azure-powershell#23406

Merged

1 task

Alancere mentioned this pull request Dec 5, 2023

[Release] sdk/resourcemanager/servicefabric/armservicefabric/2.0.0 Azure/azure-sdk-for-go#22079

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add x-ms-pageable to generate API's that support using nextlink to return resources #26369

Add x-ms-pageable to generate API's that support using nextlink to return resources #26369

Uh oh!

mwesigwaguma commented Oct 25, 2023 •

edited

Loading

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

Breaking Changes Tracking

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

Uh oh!

mwesigwaguma commented Oct 27, 2023

Uh oh!

mwesigwaguma commented Nov 1, 2023

Uh oh!

openapi-pipeline-app bot commented Nov 1, 2023

Uh oh!

Uh oh!

Add x-ms-pageable to generate API's that support using nextlink to return resources #26369

Add x-ms-pageable to generate API's that support using nextlink to return resources #26369

Uh oh!

Conversation

mwesigwaguma commented Oct 25, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Purpose of this PR

Due diligence checklist

Breaking changes review (Step 1)

ARM API changes review (Step 2)

Viewing API changes

Suppressing failures

Getting help

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Next Steps to Merge

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Swagger Validation Report

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Swagger Generation Artifacts

Breaking Changes Tracking

Uh oh!

openapi-pipeline-app bot commented Oct 25, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Generated ApiView

Uh oh!

mwesigwaguma commented Oct 27, 2023

Uh oh!

mwesigwaguma commented Nov 1, 2023

Uh oh!

openapi-pipeline-app bot commented Nov 1, 2023

Uh oh!

Uh oh!

mwesigwaguma commented Oct 25, 2023 •

edited

Loading

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading

openapi-pipeline-app bot commented Oct 25, 2023 •

edited

Loading