Expose aci v net[Do not Merge] #20696
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @subha-sam Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
"details":"" |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️LintDiff succeeded [Detail]
| Rule | Message |
|---|---|
|
"details":""stack":"ParserError: Error parsing /mnt/vss/_work/1/azure-rest-api-specs/specification/resources/resource-manager/Microsoft.Resources/stable/2022-09-01/deploymentScripts.json: unexpected end of the stream within a flow collection (963:1)\n\n 960 |
️❌Avocado: 2 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
The swagger JSON file is not referenced from the readme file. readme: specification/resources/resource-manager/readme.md json: Microsoft.Resources/stable/2022-09-01/deploymentScripts.json |
|
The example JSON file is not referenced from the swagger file. readme: specification/resources/resource-manager/readme.md json: stable/2022-09-01/examples/DeploymentScripts_Create_Using_Custom_Aci_Name_With_SubnetIds.json |
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️❌~[Staging] ServiceAPIReadinessTest: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
"\nfatal error: Unexpected end of JSON input, \n" |
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️❌ModelValidation: 0 Errors, 0 Warnings failed [Detail]
️❌SemanticValidation: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/resources/resource-manager/Microsoft.Resources/stable/2022-09-01/examples/DeploymentScripts_Create.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/resources/resource-manager/Microsoft.Resources/stable/2022-09-01/examples/DeploymentScripts_Create.json' JsonUrl: Microsoft.Resources/stable/2022-09-01/deploymentScripts.json |
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️❌PrettierCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
Code style issues found path: Microsoft.Resources/stable/2022-09-01/deploymentScripts.json |
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail]
| Rule | Message |
|---|---|
|
"details":""stack":"ParserError: Error parsing /mnt/vss/_work/1/azure-rest-api-specs/specification/resources/resource-manager/Microsoft.Resources/stable/2022-09-01/deploymentScripts.json: unexpected end of the stream within a flow collection (963:1)\n\n 960 |
️❌CadlValidation: 0 Errors, 0 Warnings failed [Detail]
️❌TypeSpec Validation: 0 Errors, 0 Warnings failed [Detail]
️❌PR Summary: 0 Errors, 0 Warnings failed [Detail]
Swagger Generation Artifacts
|
|
Hi, @subha-sam your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). |
openapi-workflow-bot
bot
added
ARMReview
WaitForARMFeedback
|
Hi @subha-sam, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Sep 13, 2022
ghost
removed
the
|
Hi, @subha-sam. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
microsoft-github-policy-service
bot
added
no-recent-activity
and removed
no-recent-activity
labels
|
Hi, @subha-sam. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
microsoft-github-policy-service
bot
added
no-recent-activity
and removed
no-recent-activity
labels
|
Hi, @subha-sam. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
@subha-sam lost access to her GH account and we will reopen the PR with her new GH account. |
|
The replacement PR is #20696 |
Merged
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
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.
-[ ] 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.