Data Plane - Microsoft.AzurePlaywrightService integration into Microsoft.LoadTestService #34012
Data Plane - Microsoft.AzurePlaywrightService integration into Microsoft.LoadTestService #34012
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
…into malt-mpt-integration-dataplane
| @doc("Creates/Updates a test-run for the workspace with given test-run id. Authorization required is Bearer JWT Access token provided by EntraID or Playwright Service.") | ||
| createOrUpdate is Operations.ResourceCreateOrUpdate<TestRun>; | ||
|
|
||
| @doc("Lists test-runs for the given workspace id. It can use OData query params like $select, $filter, $orderby, $top and $skip. The default page size is 10. Use nextLink in response to fetch more objects in the list. Authorization required is Bearer JWT Access token provided by EntraID or Playwright Service.") |
There was a problem hiding this comment.
Pls see what all filters are supported here and provide more details there
|
/azp run |
|
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. |
…into malt-mpt-integration-dataplane
|
@JeffreyRichter I think the breaking change in this PR can be approved as they are false alarm for moving files into different folders for loadtesting service. @mjmadhu I want to confirm with you that this PR is just merging the playwrightservice spec into loadtesting service, it's not adding a new service, right ? If yes, then @JeffreyRichter it's okay to sign off from the API stewardship board. If no, @mjmadhu you need to have a review meeting with them to get the sign off label. |
Hi, it's not a new spec and we've just migrated already approved/existing specs of playwright in loadtestservice RP. |
There was a problem hiding this comment.
Approved changes regarding reporting feature removal fields, but someone else should have a look as well for final approval. / @mikekistler
|
Checkout here on what's blocking the merge https://github.com/Azure/azure-rest-api-specs/pull/34012/checks?check_run_id=44581671861 |
| generate-tests: false | ||
| generate-samples: false | ||
| service-name: Load Testing | ||
| service-name: Load Test |
There was a problem hiding this comment.
@mjmadhu
Would you let me know the reason why you change the service-name?
This value affect name of Java SDK class LoadTestingServiceVersion.
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/loadtesting/azure-developer-loadtesting/src/main/java/com/azure/developer/loadtesting/LoadTestingServiceVersion.java
With this change, this class would be named LoadTestServiceVersion, and a change to public class name is a breaking change.
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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 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
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 accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext 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.