-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACI: Correct the type of httpHeaders object->array of object #19103
Conversation
Hi, @magodo 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. vscswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
R2026 - AvoidAnonymousTypes |
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1206 |
R2026 - AvoidAnonymousTypes |
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1363 |
R2026 - AvoidAnonymousTypes |
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1206 |
R2026 - AvoidAnonymousTypes |
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1363 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L520 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L791 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L853 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L876 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1678 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1683 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1746 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1750 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L2043 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L520 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L791 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L853 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L876 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1678 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1683 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1746 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1750 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L2043 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.ContainerInstance/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L415 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.ContainerInstance/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L415 |
R4037 - MissingTypeObject |
The schema 'GitRepoVolume' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1037 |
R4037 - MissingTypeObject |
The schema 'ContainerGroupIdentity' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L1333 |
R4037 - MissingTypeObject |
The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L2077 |
R4037 - MissingTypeObject |
The schema 'CloudErrorBody' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2020-11-01/containerInstance.json#L2086 |
R4037 - MissingTypeObject |
The schema 'GitRepoVolume' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1037 |
R4037 - MissingTypeObject |
The schema 'ContainerGroupIdentity' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerInstance/stable/2021-03-01/containerInstance.json#L1333 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
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).
Swagger Generation Artifacts
|
Hi @magodo, 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. |
Hi @magodo, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @magodo Please resolve the CI check failures and acquire ''breaking change' approval. Thanks |
@chunyu3 I'm just copy-paste this part from a newer API version, for the breaking changes, how to get approval, as these are actually swagger issues. |
@chunyu3 Can you please take another look at this? I think all the required checks are now passing, also the breaking change is now approved. |
…ject->array of object (#2392) Create to sync Azure/azure-rest-api-specs#19103 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...azure-sdk:sdkAuto/containerinstance?expand=1)
Fixes #18965
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
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 appy 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 are using OpenAPIHub to initialize the PR for adding a new version. 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
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.
Please follow the link to find more details on PR review process.