Update appconfiguration.json to include the "operations" path#23125
Update appconfiguration.json to include the "operations" path#23125
Conversation
|
Hi, @HarshaNalluru 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. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| appconfiguration.json | 2022-11-01-preview(48125b4) | 2022-11-01-preview(main) |
| Rule | Message |
|---|---|
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json#L1486:5 |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 4 Warnings warning [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-2022-11-01-preview | package-2022-11-01-preview(48125b4) | package-2022-11-01-preview(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| OperationId should be of the form 'Noun_Verb' Location: Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json#L1492 |
||
| Error response should contain a x-ms-error-code header. Location: Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json#L1516 |
||
Error response schema should contain an object property named error.Location: Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json#L1518 |
||
| Schema with type: integer should specify format Location: Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json#L1518 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
️️✔️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 pipeline restarted successfully, please wait for status update in this comment. |
Generated ApiView
|
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
…ration/preview/2022-11-01-preview/appconfiguration.json
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
|
NewApiVersionRequired reason: |
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
| } | ||
| } | ||
| }, | ||
| "/operations/": { |
There was a problem hiding this comment.
I understand that this is the path the API currently uses for polling URLs but I wonder if we should make it more specific (e.g. /operations/snapshot/create or something) to future-proof it in case other long-running operations are added.
There was a problem hiding this comment.
This is the URL right now.
https://endpoint.io/operations?api-version=2022-11-01-preview\u0026snapshot=snapshot-1678937759509
Service has to change if we want to be more specific here.
There was a problem hiding this comment.
Yes, this is feedback to the service team to consider. /cc @JeffreyRichter
There was a problem hiding this comment.
LRO status is generic resource. In such case our thought is that the design of the endpoint should be generic as well.
There was a problem hiding this comment.
FWIW, I didn't see a one-size-fits-all endpoint for status monitoring like this before so I wanted to make sure that future-proofing is taken into consideration. Even something like /snapshots/operations feels much safer to me. That being said, I defer to the architects on this @tg-msft @johanste @JeffreyRichter
There was a problem hiding this comment.
Our data-plane guidance is here: https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#long-running-operations--jobs. The URL for the operation COLLECTION is not LISTable and so there is no polymorphism issue. Customers can only GET a single operation and they know its type.
I'm not sure I'm addressing your question but I think I am.
...ation/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json
Outdated
Show resolved
Hide resolved
…ration/preview/2022-11-01-preview/appconfiguration.json Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
…ration/preview/2022-11-01-preview/appconfiguration.json
|
Hi @HarshaNalluru, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/examples/GetOperationStatus.json
Outdated
Show resolved
Hide resolved
…ration/preview/2022-11-01-preview/examples/GetOperationStatus.json Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
deyaaeldeen
left a comment
There was a problem hiding this comment.
LGTM. I have one comment unresolved and it is directed to the service team. Could you please share it with them? Thanks.
| }, | ||
| "error": { | ||
| "description": "An error, available when the status is `Failed`, describing why the operation failed.", | ||
| "$ref": "#/definitions/Error" |
There was a problem hiding this comment.
This isn't the correct error schema for LRO.
There was a problem hiding this comment.
@HarshaNalluru I have updated the spec to use the ErrorDetail schema defined in the Azure guidelines. could you take another look?
…23125) * Update appconfiguration.json * Update specification/appconfiguration/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json * Update specification/appconfiguration/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> * Update specification/appconfiguration/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/appconfiguration.json * Update appconfiguration.json - Deya feedback * example GetOperationStatus * Update specification/appconfiguration/data-plane/Microsoft.AppConfiguration/preview/2022-11-01-preview/examples/GetOperationStatus.json Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> * Updates to descriptions, names, id format. * Update operation status to use error detail as defined by Azure REST API guidelines. * Prettier fixes. * dummy commit for CI --------- Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> Co-authored-by: Jimmy Campbell <jimmyca@microsoft.com>
Data Plane API - Pull Request
Followup of #22840
Updates the swagger to include the "operations" path that is necessary for the lro create polling operation.