-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[Synapse] - Add 202 response scheme and LRO for job definition and SQL script #12518
[Synapse] - Add 202 response scheme and LRO for job definition and SQL script #12518
Conversation
Hi, @idear1203 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 |
---|---|
1011 - AddingResponseCode |
The new version adds a response code '202'. New: Microsoft.Synapse/preview/2019-06-01-preview/artifacts.json#L1932:11 |
1011 - AddingResponseCode |
The new version adds a response code '202'. New: Microsoft.Synapse/preview/2019-06-01-preview/artifacts.json#L2011:11 |
1011 - AddingResponseCode |
The new version adds a response code '202'. New: Microsoft.Synapse/preview/2019-06-01-preview/artifacts.json#L2155:11 |
1011 - AddingResponseCode |
The new version adds a response code '202'. New: Microsoft.Synapse/preview/2019-06-01-preview/artifacts.json#L2234:11 |
️️✔️
LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
ModelValidation: 6 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SqlScript_CreateOrUpdateSqlScript" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SqlScript_CreateOrUpdateSqlScript" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SqlScript_DeleteSqlScript" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SparkJobDefinition_CreateOrUpdateSparkJobDefinition" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SparkJobDefinition_CreateOrUpdateSparkJobDefinition" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE |
Following response status codes "202" for operation "SparkJobDefinition_DeleteSparkJobDefinition" were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. |
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
Swagger pipeline restarted successfully, please wait for status update in this comment. |
Hi @idear1203, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @idear1203, 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. |
…ure#12518) Co-authored-by: Dongwei Wang <dongwwa@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 API 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.