-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add AppPlatform 2024-07-01-preview #29179
Add AppPlatform 2024-07-01-preview #29179
Conversation
Hi @smile37773, this service has enabled ShiftLeft Toolset. All spec updates MUST be initiated from service ADO project repo, so that to guarantee it to be the source of truth., please review this pull request if it is intentional or reject it if it is not expected. Normally, all the specification or example changes should start with PR created in ADO. |
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Swagger Validation Report
|
Compared specs (v0.10.9) | new version | base version |
---|---|---|
appplatform.json | 2024-07-01-preview(bbaea0a) | 2023-12-01(main) |
appplatform.json | 2024-07-01-preview(bbaea0a) | 2024-05-01-preview(main) |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 0 Warnings warning [Detail]
Compared specs (v2.2.2) | new version | base version |
---|---|---|
package-preview-2024-07 | package-preview-2024-07(bbaea0a) | default(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
PutResponseCodes |
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.AppPlatform/preview/2024-07-01-preview/appplatform.json#L63 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L105 |
DeleteResponseCodes |
Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L134 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L158 |
UnSupportedPatchProperties |
Mark the top-level property 'location', specified in the patch operation body, as readOnly or immutable. You could also choose to remove it from the request payload of the Patch operation. This property is not patchable. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L197 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not be required, property:type. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not be required, property:frequency. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not have default value, property:name. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not have default value, property:tier. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L214 |
PostResponseCodes |
Long-running POST operations must have responses with 202 and default return codes. They must also 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. They also must not have other response codes. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L410 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L431 |
NoErrorCodeResponses |
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L434 |
NoErrorCodeResponses |
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L438 |
PostResponseCodes |
Long-running POST operations must have responses with 202 and default return codes. They must also 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. They also must not have other response codes. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L458 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L479 |
NoErrorCodeResponses |
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L482 |
NoErrorCodeResponses |
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L486 |
PostResponseCodes |
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.AppPlatform/preview/2024-07-01-preview/appplatform.json#L641 |
PostResponseCodes |
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.AppPlatform/preview/2024-07-01-preview/appplatform.json#L701 |
XmsPageableForListCalls |
x-ms-pageable extension must be specified for LIST APIs.Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1007 |
EvenSegmentedPathForPutOperation |
API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments). Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1048 |
XmsPageableForListCalls |
x-ms-pageable extension must be specified for LIST APIs.Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1049 |
EvenSegmentedPathForPutOperation |
API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments). Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1218 |
XmsPageableForListCalls |
x-ms-pageable extension must be specified for LIST APIs.Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1219 |
ProvisioningStateSpecifiedForLROPut |
201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1262 |
PutResponseCodes |
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.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1262 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1298 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not be required, property:uri. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1345 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1357 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView 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.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️
Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
Add allowed resources for ACS
Close pull request |
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
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 ApiView
comment 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 PR
andDue diligence checklist
.Next Steps to Merge
comment. 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.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.