-
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
Microsoft.IoTSecurity - Add locations and deviceSecurityGroups #13091
Conversation
Hi, @liranc 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. vsswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'ErrorResponseModel-error' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'Resource' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'ProxyResource' with an undefined type and 'allOf'/'anyOf'/'oneOf' is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'ErrorDetail' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'ErrorResponse' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"The schema 'ErrorAdditionalInfo' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"iotsecurity/resource-manager/readme.md", "tag":"2021-02-01-preview", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
Hi @liranc, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...security/resource-manager/Microsoft.IoTSecurity/preview/2021-02-01-preview/deviceGroups.json
Show resolved
Hide resolved
...security/resource-manager/Microsoft.IoTSecurity/preview/2021-02-01-preview/deviceGroups.json
Show resolved
Hide resolved
"readOnly": true, | ||
"type": "object", | ||
"description": "Azure Resource Manager metadata containing createdBy and modifiedBy information.", | ||
"$ref": "../../../../../common-types/resource-management/v2/types.json#/definitions/systemData" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure having systemData for location makes sense since there is no way for users to create a location..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@j5lim Is systemData
optional for proxy resources?
On a separate PR, we've attempted to create a new proxy resource without systemData
but received a CI validation error, saying the property must be defined.
Can this error be ignored for proxy resources?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ARM guideline says it should be supported by all resources, but I mean in this particular case it does not make sense to me. Wondering there is a way to suppress the CI validation.. @ruowan do you know if it's possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@liranc You can leave it as it is if it causes a CI failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@j5lim Can the PR be merged in that case, or are there any other action items left? 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@liranc Please work with the pr assignee to get the pr merged. ARM team does not have merge permission.
…#13091) * Locations * v1 * v2 * v3 * File rename * Rename resource * Update common types file path * add pageable option * Add missing nextLink property Co-authored-by: Liran Chen <lirche@microsoft.com>
…#13091) * Locations * v1 * v2 * v3 * File rename * Rename resource * Update common types file path * add pageable option * Add missing nextLink property Co-authored-by: Liran Chen <lirche@microsoft.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with 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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.