[DevCenter] [Microsoft.DevCenter] [Dataplane] Add new stable api version 2025-02-01

[snehanagendra]

Data 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.

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.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

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.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

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.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the 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.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in 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.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
.Net	Azure.Developer.DevCenter	https://apiview.dev/Assemblies/Review/e8a17bbdc15f43afb87666d4fb36f09c?revisionId=bba606e8a16c48379ffb4cf3c6eb4396
Java	azure-developer-devcenter	https://apiview.dev/Assemblies/Review/77592e1c02504994a45ad468b6905fbe?revisionId=a53e0c5607ac40558b2289e0e6f72542
Python	azure-developer-devcenter	https://apiview.dev/Assemblies/Review/b8a03e20f41e4d7d80037a319a715de1?revisionId=df55e458120f44fea8e4fcf5a31046cb

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.DevCenter

[tbyfield]

LGTM

[mikekistler]

This mostly looks fine but I left one comment on a minor issue I hope we can get cleaned up.

[weidongxu-microsoft]

Update the client.tsp to use the stable api-version

azure-rest-api-specs/specification/devcenter/DevCenter/client.tsp

Line 9 in ab02b54

@useDependency(APIVersions.v2024_09_01_preview)

Also you may want to include the latest APIs. E.g. captureSnapshot is not in client.tsp
The fine tuning of this file can be done later with the involvement of SDK dev. But it would be helpful to have something first so we can see how SDK becomes, on your stable API.

[weidongxu-microsoft]

LGTM

I've got one comment about outdated client.tsp #32290 (comment)
It is not required for the PR merge, but it would help your SDK work, if issue can be found earlier.

[ArberH]

LGTM

I've got one comment about outdated client.tsp #32290 (comment) It is not required for the PR merge, but it would help your SDK work, if issue can be found earlier.

Someone on our team will begin on the SDK work after this gets merged in. We're going to leave as is for now. Would appreciate a re-approval with our latest pushes. Thanks!

[mikekistler]

Looks good! 👍

[ArberH]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

[ArberH]

/azp run openapi-pipeline-app

[azure-pipelines]

No pipelines are associated with this pull request.

[nickdepinet]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.