Skip to content
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

Release playwrighttesting microsoft.playwright testing.auth manager 2024 12 01 #31855

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

mjmadhu
Copy link
Member

@mjmadhu mjmadhu commented Dec 12, 2024

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.

spec_pr_review_workflow_diagram

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.

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

Tooling

Guidelines & Specifications

Helpful Links

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.

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2023-10-01-preview to stable/2024-12-01.
@mjmadhu mjmadhu requested a review from a team as a code owner December 12, 2024 09:26
@mjmadhu mjmadhu requested review from allenjzhang and mario-guerra and removed request for a team December 12, 2024 09:26
Copy link

openapi-pipeline-app bot commented Dec 12, 2024

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This is the public specs repo main branch which is not intended for iterative development.
    You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
    If this is what you intend, add PublishToCustomers label to your PR.
    Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ Your PR requires an API stewardship board review as it introduces a new API version (label: new-api-version). Schedule the review by following aka.ms/azsdk/onboarding/restapischedule.
  • ❌ The required check named Swagger LintDiff has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Copy link

openapi-pipeline-app bot commented Dec 12, 2024

@mjmadhu mjmadhu enabled auto-merge (squash) December 12, 2024 09:31
@mjmadhu mjmadhu changed the base branch from release-playwrighttesting-Microsoft.PlaywrightTesting.AuthManager-2024-12-01-devv to release-playwrighttesting-Microsoft.PlaywrightTesting.AuthManager-2024-12-01 December 12, 2024 10:21
@mjmadhu mjmadhu changed the title Rectified a typo Added stable api-version for data-plane auth manager apis Dec 12, 2024
@mjmadhu mjmadhu added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Dec 17, 2024
Copy link
Member

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. 👍

Left one minor comment on eliminating uncommon acronyms.

"/accounts/{accountId}/access-tokens/validate": {
"post": {
"operationId": "AccessTokens_Validate",
"description": "Validates access-token provided in authorization header for the given account id. Authorization required is Bearer JWT Access token provided by MPT service.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here and in a few other spots there is the acronym "MPT" -- is this "Microsoft Playwright Service"? It might be better to spell this out.

@mikekistler mikekistler linked an issue Dec 21, 2024 that may be closed by this pull request
Comment on lines +209 to +213
@doc("Linux OS.")
Linux: "linux",

@doc("Windows OS.")
Windows: "windows",
Copy link
Member

@weidongxu-microsoft weidongxu-microsoft Dec 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a blocker, but we'd expect the casing of enum values be consistent. Here is it lowercase/camelCase e.g. linux, and the enum value above is PascalCase e.g. Active. Any reason for this inconsistency?

Comment on lines +248 to +250
@path
@doc("The account id.")
accountId: string;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure how much it effects the Swagger or API. But I'd expect the most important parameter (I assume it be accountId) at the top.

Comment on lines 108 to +114
@doc("When enabled, this feature allows the workspace to upload and display test results, including artifacts like traces and screenshots, in the Playwright portal. This enables faster and more efficient troubleshooting.")
@visibility("read")
reporting?: EnablementStatus = EnablementStatus.Disabled;
reporting?: EnablementStatus = EnablementStatus.Enabled;

@doc("When enabled, this feature allows the workspace to use local auth (through service access token) for executing operations.")
@visibility("read")
localAuth?: EnablementStatus = EnablementStatus.Disabled;
Copy link
Member

@weidongxu-microsoft weidongxu-microsoft Dec 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why there is a service-side default value (e.g. EnablementStatus.Disabled) to this already read-only property?
A server-side default value is used when user does not define the property in request (e.g. a PUT), and server choose the value. How does this work together with a property user cannot set?

And since the e.g. localAuth? is an optional property, what does it mean, when the response does not contain localAuth. Is it "disabled" or "enabled"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Playwright-DevDiv-Service - Playwright] API Review
8 participants