[test render ]Update datafactory.json #3330
Closed
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
mgmt_tsp_automation_conf
switch java branch override
Next Steps to mergeNext steps that must be taken to merge this PR:
|
Swagger Generation Artifacts
|
Generated ApiView
|
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
"new":"https://github.com/test-repo-billy/azure-rest-api-specs/blob/39b325bd644dd489b69b1b889e9e5312dfb999a4/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json", "old":"https://github.com/test-repo-billy/azure-rest-api-specs/blob/main/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json", "details":"incompatible properties : properties\n definitions/ManagedIdentityCredentialResource/properties/properties\n at file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L7683:8\n definitions/CredentialResource/properties/properties\n at file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L7983:8" |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️❌LintDiff: 1 Errors, 0 Warnings failed [Detail]
| Compared specs (v2.2.0) | new version | base version |
|---|---|---|
| package-2018-06 | package-2018-06(39b325b) | package-2018-06(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
|
The top-level resource 'Factory' does not have list by subscription operation, please add it. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L6128 |
RPC-Get-V1-05 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The response schema of operations API '/providers/Microsoft.DataFactory/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L56 |
|
Operations API path must follow the schema provided in the common types. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L57 |
|
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L313 |
|
Properties of a PATCH request body must not be required, property:type. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L398 |
|
GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L418 |
|
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L457 |
|
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L657 |
|
GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L716 |
|
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L758 |
|
The property 'autoUpdate' in the request body either not apppear in the resource model or has the wrong level. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L801 |
|
The property 'updateDelayOffset' in the request body either not apppear in the resource model or has the wrong level. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L801 |
|
x-ms-pageable extension must be specified for LIST APIs.Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L911 |
|
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L942 |
|
A 202 response should include an Location response header. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1136 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1142 |
|
200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1149 |
|
A 202 response should include an Location response header. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1182 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1188 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'IntegrationRuntimes' 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.DataFactory/stable/2018-06-01/datafactory.json#L1379 |
|
A 202 response should include an Location response header. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1465 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1471 |
|
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1774 |
|
GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1836 |
|
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1878 |
|
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1979 |
|
GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2041 |
|
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2083 |
|
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2184 |
|
GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2246 |
|
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2288 |
️️✔️[ignore this check status; not blocking PR merge] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️❌Avocado: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
The example JSON file is not referenced from the swagger file. readme: specification/datafactory/resource-manager/readme.md json: stable/2018-06-01/examples/Factories_List.json |
️❌ModelValidation: 83 Errors, 0 Warnings failed [Detail]
Only 30 items are listed, please refer to log for more details.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[ignore this check status; not blocking PR merge] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️PR Summary succeeded [Detail] [Expand]
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
This was referenced Apr 26, 2024
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
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.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.Note
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.
Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.
Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.Next Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.