-
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
Adding DisableLocalAuth property in PUT payload #15819
Conversation
Hi, @chsamala2 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] |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Rule | Message |
---|---|
1045 - AddedOptionalProperty |
The new version has a new optional property 'disableLocalAuth' that was not found in the old version. New: Microsoft.Automation/stable/2021-06-22/account.json#L623:7 Old: Microsoft.Automation/stable/2021-06-22/account.json#L623:7 |
️⚠️
LintDiff: 1 Warnings warning [Detail]
- Linted configuring files (Based on source branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
- Linted configuring files (Based on target branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
Rule | Message |
---|---|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disableLocalAuth Location: Microsoft.Automation/stable/2021-06-22/account.json#L636 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
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.Automation/stable/2021-06-22/account.json#L890 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L84 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L142 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L185 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L228 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L270 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L310 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L365 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L413 |
R4007 - DefaultErrorResponseSchema |
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.Automation/stable/2021-06-22/account.json#L458 |
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.Automation/stable/2021-06-22/hybridRunbookWorkerGroup.json#L75 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.Automation/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.Automation/stable/2021-06-22/operations.json#L39 |
R4037 - MissingTypeObject |
The schema 'AutomationAccount' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L469 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L495 |
R4037 - MissingTypeObject |
The schema 'Sku' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L563 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountCreateOrUpdateParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L592 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountCreateOrUpdateProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L622 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L643 |
R4037 - MissingTypeObject |
The schema 'Statistics' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L659 |
R4037 - MissingTypeObject |
The schema 'StatisticsListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L694 |
R4037 - MissingTypeObject |
The schema 'Usage' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L706 |
R4037 - MissingTypeObject |
The schema 'UsageCounterName' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L737 |
R4037 - MissingTypeObject |
The schema 'UsageListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L750 |
R4037 - MissingTypeObject |
The schema 'Key' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L762 |
R4037 - MissingTypeObject |
The schema 'KeyListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L798 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountUpdateProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L809 |
R4037 - MissingTypeObject |
The schema 'AutomationAccountUpdateParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L830 |
R4037 - MissingTypeObject |
The schema 'Identity' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L860 |
R4037 - MissingTypeObject |
The schema 'EncryptionProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L908 |
R4037 - MissingTypeObject |
The schema 'identity' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Automation/stable/2021-06-22/account.json#L927 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/automation/resource-manager/readme.md tag: specification/automation/resource-manager/readme.md#tag-package-2020-01-13-preview |
️️✔️
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.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
|:speech_balloon: AutorestCore/Exception|"readme":"automation/resource-manager/readme.md",
"tag":"package-2021-06-22",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"automation/resource-manager/readme.md",
"tag":"package-2021-06-22",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
The following errors/warnings exist before current PR submission:
|:speech_balloon: AutorestCore/Exception|"readme":"automation/resource-manager/readme.md",
"tag":"package-2021-06-22",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
NewApiVersionRequired reason: |
New API Version- API Version : 2021-06-22 is added as part of Another PR - #14956 , which is merged yesterday and we have not released to public so far. So We dont need new API version. |
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 apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] 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.
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.