-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adding new ACA Session Data Plane APIs #31996
base: main
Are you sure you want to change the base?
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
Thank you for your contribution shivamkm07! We will review the pull request and get back to you soon. |
API change check APIView has identified API level changes in this PR and created following API reviews. |
API change check APIView has identified API level changes in this PR and created following API reviews. |
...fication/app/Microsoft.App.DynamicSessions/examples/2024-10-02-preview/ListSessions_Get.json
Show resolved
Hide resolved
...ion/app/Microsoft.App.DynamicSessions/examples/2024-10-02-preview/SessionManagement_Get.json
Outdated
Show resolved
Hide resolved
...n/app/Microsoft.App.DynamicSessions/examples/2024-10-02-preview/SessionPoolMetadata_Get.json
Outdated
Show resolved
Hide resolved
specification/app/Microsoft.App.DynamicSessions/models/session.tsp
Outdated
Show resolved
Hide resolved
@get | ||
get is Foundations.Operation<SessionIdentifier, Session>; | ||
|
||
#suppress "@azure-tools/typespec-azure-core/use-standard-operations" "No suitable standard operation found." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we avoid these suppression as it means they are not following standard pattern ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I tried to use resource
Operations which is the standard, but that requires resource Id i.e sessionIdentifier added in the URL Path instead of query params, which is not what we follow for other data-plane APIs. So these suppressions are required.
Signed-off-by: Shivam Kumar <[email protected]>
Signed-off-by: Shivam Kumar <[email protected]>
Signed-off-by: Shivam Kumar <[email protected]>
Signed-off-by: Shivam Kumar <[email protected]>
|
||
@route("/listSessions") | ||
interface ListSessions { | ||
#suppress "@azure-tools/typespec-azure-core/use-standard-operations" "No suitable standard operation found." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be helpful to add the reason of suppression in comments
"$ref": "#/parameters/Azure.Core.Foundations.ApiVersionParameter" | ||
}, | ||
{ | ||
"name": "offset", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this word "offset" the correct word to be used according to Azure API guidelines? Did you see this "offset" word recommended somewhere or did you comeup with it?
"format": "int32" | ||
}, | ||
{ | ||
"name": "limit", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment for this word "limit" as well. From what I remember there are recommended words to use. Can you check once incase you haven't checked?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The above comments are just suggestions, you can ignore them unless API review team asks you to update.
Anyways, according to the guidelines I see that recommended words are "maxpagesize" instead of "limit" and "skip" instead of "offset" words.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The guidelines are here: https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#query-options
"sessions": { | ||
"type": "array", | ||
"description": "The list of sessions.", | ||
"items": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a suggestion, ignore if not relevant: Do we want to send "nextLink" field in the response body with an absolute URL that the client can GET in order to retrieve the next page of the collection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR pipeline tooling is failing because of a bad example file that is already merged to main:
CodeExecution_Execute_Async_Running.json
The problem is that the headers
field is not allowed here. It should be included in the parameters
section.
A quick check of the other example files found a second occurrence of this problem in
CodeExecution_Execute_Async_Completed.json
Please open a separate PR to correct this problem (fixing just these files)
The runtime failure in the PR tooling obscures a deviation from the Azure Versioning policy. The 2024-10-02-preview API version was already merged to main in the public repo, so updates to this version must be done in a new API version. I've added the VersioningReviewRequired label by hand to signal this.
Data Plane API Specification Update Pull Request
Related PR: https://msazure.visualstudio.com/One/_git/AAPT-Antares-Containerapps/pullrequest/11352385
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.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
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
Swagger-Suppression-Process
to get approval.
❔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
Getting help
write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext 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.