-
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
[Hub Generated] Review request for Microsoft.Logic to add version stable/2019-05-01 #16181
[Hub Generated] Review request for Microsoft.Logic to add version stable/2019-05-01 #16181
Conversation
Hi, @rarayudu 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 |
[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 |
---|---|
Guid used in model definition 'ManagedServiceIdentity' for property 'tenantId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L9152 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6291 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L7770 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L8056 |
R4013 - IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L8060 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.Logic/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6367 |
R4037 - MissingTypeObject |
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6405 |
R4037 - MissingTypeObject |
The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6437 |
R4037 - MissingTypeObject |
The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12184 |
'PUT' operation 'IntegrationServiceEnvironmentManagedApis_Put' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6183 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L8174 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L8605 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L8834 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12762 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12863 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12951 |
|
The operation 'WorkflowTriggers_Run' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L1096 |
|
The operation 'WorkflowTriggerHistories_Resubmit' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L1543 |
|
Sku Model definition 'Sku' is not valid. A Sku model must have 'name' property. It can also have 'tier', 'size', 'family', 'capacity' as optional properties. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L7307 |
|
OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'IntegrationServiceEnvironmentNetworkHealthModel'. Consider using the plural form of 'IntegrationServiceEnvironmentNetworkHealth' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6025 |
|
The child tracked resource, 'versions' with immediate parent 'Workflow', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6587 |
|
The child tracked resource, 'triggers' with immediate parent 'Workflow', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6686 |
|
The child tracked resource, 'histories' with immediate parent 'WorkflowTrigger', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6857 |
|
The child tracked resource, 'runs' with immediate parent 'Workflow', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6978 |
|
The child tracked resource, 'actions' with immediate parent 'WorkflowRun', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L7103 |
|
The child tracked resource, 'repetitions' with immediate parent 'WorkflowRunAction', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12552 |
|
The child tracked resource, 'requestHistories' with immediate parent 'WorkflowRunActionRepetitionDefinition', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12946 |
|
The child tracked resource, 'requestHistories' with immediate parent 'WorkflowRunAction', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12946 |
|
The child tracked resource, 'scopeRepetitions' with immediate parent 'WorkflowRunAction', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12552 |
|
The child tracked resource, 'operations' with immediate parent 'WorkflowRun', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L6978 |
|
The child tracked resource, 'assemblies' with immediate parent 'IntegrationAccount', must have a list by immediate parent operation. Location: Microsoft.Logic/stable/2019-05-01/logic.json#L12754 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
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
️️✔️
[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: |
Hi @rarayudu, 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. |
Regarding the breaking change comment - This PR is to mainly fix the bugs that we found while generating the Terraform SDK. The API already has been released long time back and the API responds back with the updates response. |
...crosoft.Logic/stable/2019-05-01/examples/IntegrationServiceEnvironments_ManagedApis_Put.json
Show resolved
Hide resolved
specification/logic/resource-manager/Microsoft.Logic/stable/2019-05-01/logic.json
Show resolved
Hide resolved
specification/logic/resource-manager/Microsoft.Logic/stable/2019-05-01/logic.json
Outdated
Show resolved
Hide resolved
specification/logic/resource-manager/Microsoft.Logic/stable/2019-05-01/logic.json
Show resolved
Hide resolved
specification/logic/resource-manager/Microsoft.Logic/stable/2019-05-01/logic.json
Show resolved
Hide resolved
@rarayudu , can you follow above action for breaking change review? |
…ble/2019-05-01 (Azure#16181) * Fixing bugs in Logic Apps swaggers * Updating example * Addressed feedback
…ble/2019-05-01 (Azure#16181) * Fixing bugs in Logic Apps swaggers * Updating example * Addressed feedback
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.