Adding API readiness tests for AMS #22428

giakas · 2023-02-02T08:23:23Z

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-02-02T08:23:26Z

Hi, @giakas 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-02-02T08:23:27Z

Swagger Validation Report

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

There are no breaking changes.

compared swaggers (via Oad v0.10.4)]	new version	base version
Accounts.json	2021-11-01(a970719)	2021-11-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-preview-2022-05	package-preview-2022-05(a970719)	package-preview-2022-05(main)
package-encoding-2022-07	package-encoding-2022-07(a970719)	package-encoding-2022-07(main)
package-metadata-2022-08	package-metadata-2022-08(a970719)	package-metadata-2022-08(main)
package-2022-08	package-2022-08(a970719)	package-2022-08(main)
package-account-2021-11	package-account-2021-11(a970719)	package-account-2021-11(main)

The following errors/warnings exist before current PR submission:

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

Rule	Message
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L411
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L411
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L411
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L411
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L411
`❌` ProvisioningStateValidation	ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Accounts/stable/2021-11-01/Accounts.json#L476
`❌` ProvisioningStateValidation	ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Accounts/stable/2021-11-01/Accounts.json#L476
`❌` ProvisioningStateValidation	ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Accounts/stable/2021-11-01/Accounts.json#L476
`❌` ProvisioningStateValidation	ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Accounts/stable/2021-11-01/Accounts.json#L476
`❌` ProvisioningStateValidation	ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Accounts/stable/2021-11-01/Accounts.json#L476
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L632
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L632
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L632
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L632
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L632
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L639
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L639
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L639
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L639
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L639
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L658
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L658
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L658
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L658
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L658
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L665
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L665
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L665
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L665
`❌` GuidUsage	Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Accounts/stable/2021-11-01/Accounts.json#L665

️⚠️Avocado: 1 Warnings warning [Detail]

Rule	Message
⚠️ MULTIPLE_API_VERSION	The default tag contains multiple API versions swaggers. readme: specification/mediaservices/resource-manager/readme.md tag: specification/mediaservices/resource-manager/readme.md#tag-package-encoding-2022-07

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

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

Validation passes for ServiceAPIReadinessTest.

Tag package-encoding-2022-07; Prod region: Deployed

Test run on region: westcentralus; Operation coverage: total: 99, untested: 30, failed: 0, passed: 69

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

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

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

openapi-pipeline-app · 2023-02-02T08:23:28Z

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-net-track2 succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from d66735f. 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.Media [View full logs] [Release SDK Changes]
- Azure.ResourceManager.Media.1.2.0-alpha.20230208.1.nupkg
```
info	[Changelog]
```

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

⚠️Warning [Logs]Release - Generate from d66735f. 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.3 -> 9.4.2
cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.4.2>
cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.4.2` to update!
cmderr	[automation_generate.sh] npm notice

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

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

⚠️Warning [Logs]Release - Generate from d66735f. 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.1 -> 23.0
cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
cmderr	[init.sh] [notice] A new release of pip available: 22.3.1 -> 23.0
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
cmderr	[generate.py] [ForkJoinPool-1-worker-3] INFO com.azure.core.test.implementation.TestingHelpers - Environment variable 'AZURE_TEST_MODE' has not been set yet. Using 'Playback' mode.

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

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

️✔️Succeeded [Logs]Release - Generate from d66735f. 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/mediaservices/armmediaservices [View full logs] [Release SDK Changes]

info	[Changelog] ### Other Changes
info	[Changelog]
info	[Changelog] Total 0 breaking change(s), 0 additive change(s).

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

️✔️Succeeded [Logs]Release - Generate from d66735f. 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
cmderr	[automation_generate.sh] [ERROR] Cannot generate changelog because the codes of local and npm may be the same.

️✔️@azure/arm-mediaservices [View full logs] [Release SDK Changes]
- azure-arm-mediaservices-13.1.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 d66735f. 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

️✔️mediaservices [View full logs]

️❌ azure-powershell failed [Detail]

❌Failed [Logs]Release - Generate from d66735f. 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.mediaservices [View full logs] [Release SDK Changes]

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

openapi-pipeline-app · 2023-02-02T08:23:29Z

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/mediaservices/armmediaservices	https://apiview.dev/Assemblies/Review/2b271c2b667f4998935f2af5332b4450
.Net	Azure.ResourceManager.Media	There is no API change compared with the previous version
Java	azure-resourcemanager-mediaservices	There is no API change compared with the previous version
JavaScript	@azure/arm-mediaservices	There is no API change compared with the previous version

tianxchen-ms · 2023-02-03T02:29:34Z

/azp run

azure-pipelines · 2023-02-03T02:29:43Z

Azure Pipelines successfully started running 1 pipeline(s).

This reverts commit 869ebd6.

openapi-workflow-bot · 2023-02-06T08:27:53Z

Hi @giakas, 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

If you need further help, please feedback via swagger feedback.

tianxchen-ms · 2023-02-07T02:15:37Z

/azp run

azure-pipelines · 2023-02-07T02:15:47Z

Azure Pipelines successfully started running 1 pipeline(s).

…Version When a service is split-up into different sub-groupings within the Swagger, we need to account for the fact that an API version may not be available in all of the sub-groups. This fixes an issue introduced in Azure/azure-rest-api-specs#22428 where the Media Service has introduced a new sub-group with no Swagger files, meaning importing this currently panics: ``` 2023-02-08T11:36:08.401Z [INFO] Importer for Service "Media".Importer for API Version "2022-08-01": 😵 Service "Media" / Api Version "2022-08-01" contains no resources, skipping. 215 panic: runtime error: invalid memory address or nil pointer dereference 216 [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xac65d4] 217 218 goroutine 1 [running]: 219 github.com/hashicorp/pandora/tools/importer-rest-api-specs/pipeline.runImportForService({{0xca2f0d, 0x21}, 0x0, 0x0, 0x0, {0xdde440, 0xc000187710}, {0xc8a2a1, 0xb}, {0xc87687, ...}, ...}, ...) 220 /home/runner/work/pandora/pandora/tools/importer-rest-api-specs/pipeline/run_importer.go:94 +0x1094 221 github.com/hashicorp/pandora/tools/importer-rest-api-specs/pipeline.runImporter({{0xca2f0d, 0x21}, 0x0, 0x0, 0x0, {0xdde440, 0xc000187710}, {0xc8a2a1, 0xb}, {0xc87687, ...}, ...}, ...) 222 /home/runner/work/pandora/pandora/tools/importer-rest-api-specs/pipeline/run_importer.go:39 +0x3b9 223 github.com/hashicorp/pandora/tools/importer-rest-api-specs/pipeline.Run({{0xca2f0d, 0x21}, 0x0, 0x0, 0x0, {0xdde440, 0xc000187710}, {0xc8a2a1, 0xb}, {0xc87687, ...}, ...}) 224 /home/runner/work/pandora/pandora/tools/importer-rest-api-specs/pipeline/interface.go:66 +0x4a5 225 github.com/hashicorp/pandora/tools/importer-rest-api-specs/cmd.ImportCommand.Run({{0xc8a2a1, 0xb}, {0xca2f0d, 0x21}, {0xc8be69, 0xd}, {0xc96634, 0x17}}, {0xc000124010, 0x0, ...}) 226 /home/runner/work/pandora/pandora/tools/importer-rest-api-specs/cmd/import.go:85 +0x4c5 227 github.com/mitchellh/cli.(*CLI).Run(0xc0003492c0) 228 /home/runner/go/pkg/mod/github.com/mitchellh/cli@v1.1.4/cli.go:262 +0x5f8 229 main.main() 230 /home/runner/work/pandora/pandora/tools/importer-rest-api-specs/main.go:31 +0x353 ```

* Adding API readiness tests for AMS * fix lint errors * fix prettier issues * rename rg * try use file as scope * Revert "try use file as scope" This reverts commit 869ebd6. * tiny fix * fix rg name * fix job name * fix job name * fix a model validation * remove job cancel step. * fix a failure --------- Co-authored-by: Lei Ni <leni@microsoft.com> Co-authored-by: Tianxiang Chen <tianxchen@microsoft.com>

Adding API readiness tests for AMS

0c9c171

ghost added the Media Services label Feb 2, 2023

azure-sdk mentioned this pull request Feb 2, 2023

[AutoPR sdk/resourcemanager/mediaservices/armmediaservices] Adding API readiness tests for AMS azure-sdk/azure-sdk-for-go#4168

Closed

AzureRestAPISpecReview added the resource-manager label Feb 2, 2023

giakas added 2 commits February 2, 2023 00:52

fix lint errors

2002361

fix prettier issues

600d56f

openapi-workflow-bot bot added the FixS360 label Feb 2, 2023

giakas marked this pull request as ready for review February 2, 2023 09:19

openapi-assignment-bot bot assigned allenjzhang Feb 2, 2023

akning-ms assigned leni-msft and unassigned allenjzhang Feb 2, 2023

giakas removed the FixS360 label Feb 3, 2023

tianxchen-ms added the ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test label Feb 3, 2023

leni-msft added 4 commits February 6, 2023 15:00

rename rg

d10b0fb

try use file as scope

869ebd6

Revert "try use file as scope"

dc1953e

This reverts commit 869ebd6.

tiny fix

ef778b4

AzureRestAPISpecReview added the CI-FixRequiredOnFailure label Feb 6, 2023

fix rg name

07a83d1

Tianxiang Chen and others added 3 commits February 7, 2023 10:26

fix job name

762ea25

fix job name

a188c8c

fix a model validation

5e51f85

AzureRestAPISpecReview removed the CI-FixRequiredOnFailure label Feb 7, 2023

giakas added 2 commits February 7, 2023 11:15

remove job cancel step.

5f480a1

fix a failure

a970719

tianxchen-ms approved these changes Feb 8, 2023

View reviewed changes

leni-msft merged commit d66735f into main Feb 8, 2023

tombuildsstuff mentioned this pull request Feb 8, 2023

tools/importer: fixing a crash when there's no files for a given API Version hashicorp/pandora#2089

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adding API readiness tests for AMS #22428

Adding API readiness tests for AMS #22428

giakas commented Feb 2, 2023 •

edited

Loading

openapi-workflow-bot bot commented Feb 2, 2023

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading

Breaking Changes Tracking

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading

tianxchen-ms commented Feb 3, 2023

azure-pipelines bot commented Feb 3, 2023

openapi-workflow-bot bot commented Feb 6, 2023

tianxchen-ms commented Feb 7, 2023

azure-pipelines bot commented Feb 7, 2023

Adding API readiness tests for AMS #22428

Adding API readiness tests for AMS #22428

Conversation

giakas commented Feb 2, 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 Feb 2, 2023

openapi-pipeline-app bot commented Feb 2, 2023 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Feb 2, 2023 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-pipeline-app bot commented Feb 2, 2023 • edited Loading

Generated ApiView

tianxchen-ms commented Feb 3, 2023

azure-pipelines bot commented Feb 3, 2023

openapi-workflow-bot bot commented Feb 6, 2023

tianxchen-ms commented Feb 7, 2023

azure-pipelines bot commented Feb 7, 2023

giakas commented Feb 2, 2023 •

edited

Loading

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading

openapi-pipeline-app bot commented Feb 2, 2023 •

edited

Loading