Renaming definitions from Bulk Jobs to Import Jobs #22488
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abhinav-ghai
requested review from
JeffreyRichter and
MushMal
and removed request for
a team
|
Hi, @abhinav-ghai 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] |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| digitaltwins.json | 2023-02-27-preview(cc1848b) | 2023-02-27-preview(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-preview-2023-02-27 | package-preview-2023-02-27(cc1848b) | package-preview-2023-02-27(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Per the Noun_Verb convention for Operation Ids, the noun 'Query' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L268 |
|
The schema 'ErrorResponse' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1762 |
|
The schema 'Error' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1774 |
|
The schema 'InnerError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1801 |
|
The parameter 'api-version' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1880 |
|
The integer type does not have a format, please add it. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1888 |
|
The enum types should have x-ms-enum type extension set with appropriate options. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L1900 |
| Using post for a create operation is discouraged. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L59 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L65 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L67 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L119 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L121 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L152 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L169 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L171 |
|
| A patch operation should consume 'application/merge-patch+json' content type. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L183 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L192 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L215 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L217 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L235 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L246 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L248 |
|
| Since operation response has model definition in array type, it should be of the form '_list'. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L264 |
|
| Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L264 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L311 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L313 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L341 |
|
| Error response should contain a x-ms-error-code header. Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L361 |
|
Error schema should define code and message properties as required.Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L363 |
|
| A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'DigitalTwins_Add' Request Model: 'parameters[1].schema' Response Model: 'responses[200].schema' Location: Microsoft.DigitalTwins/preview/2023-02-27-preview/digitaltwins.json#L369 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️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).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
AzureRestAPISpecReview
added
BreakingChangeReviewRequired
|
Hi @abhinav-ghai, 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. |
|
We haven't released the SDK or Docs from this swagger yet, so these are not breaking changes. |
rachelsophia
reviewed
Feb 7, 2023
...ta-plane/Microsoft.DigitalTwins/preview/2023-02-27-preview/examples/BulkImportJobCancel.json
Show resolved
Hide resolved
JeffreyRichter
added
the
Approved-BreakingChange
MushMal
approved these changes
Feb 7, 2023
anuchandy
approved these changes
Feb 8, 2023
aviyerMSFT
pushed a commit
to aviyerMSFT/azure-rest-api-specs
that referenced
this pull request
Mar 22, 2023
* Renaming definitions from Bulk Jobs to Import Jobs * Rename files to exclude Bulk from examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Data Plane API - Pull Request
Renaming some definition names and description to suit our naming pattern. API remains same.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.
Is this review for (select one):
Change Scope
This PR involves renaming certain artifacts so that the generated docs reflect proper naming scheme.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links