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

[Identity] Testing service connections on pipeline #29451

Merged
merged 13 commits into from Apr 30, 2024

Conversation

KarishmaGhiya
Copy link
Contributor

@KarishmaGhiya KarishmaGhiya commented Apr 26, 2024

  • Testing whether OIDC API 7.1 is available or not. Unfortunately, it's not available. So we only ship a preview with 7.1-preview.1
    Response = {"$id":"1","innerException":null,"message":"The requested version "7.1" of the resource is under preview. The -preview flag must be supplied in the api-version for such requests. For example: "7.1-preview"","typeName":"Microsoft.VisualStudio.Services.WebApi.VssInvalidPreviewVersionException, Microsoft.VisualStudio.Services.WebApi","typeKey":"VssInvalidPreviewVersionException","errorCode":0,"eventId":3000}

@azure-sdk
Copy link
Collaborator

azure-sdk commented Apr 26, 2024

API change check

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

@azure/identity

@KarishmaGhiya KarishmaGhiya changed the title Testpipeline [Identity] Test pipeline Apr 26, 2024
@KarishmaGhiya KarishmaGhiya changed the title [Identity] Test pipeline [Identity] Testing service connections on pipeline Apr 26, 2024
Copy link
Member

@maorleger maorleger left a comment

Choose a reason for hiding this comment

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

Few things I noticed but otherwise LGTM

describe("AzurePipelinesServiceConnectionCredential", function () {
const scope = "https://vault.azure.net/.default";
const tenantId = env.IDENTITY_SP_TENANT_ID || env.AZURE_TENANT_ID!;
const tenantId = "72f988bf-86f1-41af-91ab-2d7cd011db47";
Copy link
Member

Choose a reason for hiding this comment

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

when we record these tests, you'd want any env. calls to be made after the recorder is initialized (so like in the test body or a beforeEach block after creating the recorder. Just FYI. I could be wrong but I remember this being a problem for me

Copy link
Contributor Author

Choose a reason for hiding this comment

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

True. Though with this particular test, it's difficult to have recordings, since I cannot run locally :(

…nnection.spec.ts

Co-authored-by: Maor Leger <maorleger@users.noreply.github.com>
@KarishmaGhiya KarishmaGhiya enabled auto-merge (squash) April 29, 2024 21:14
@KarishmaGhiya KarishmaGhiya enabled auto-merge (squash) April 30, 2024 00:32
@KarishmaGhiya KarishmaGhiya merged commit a1e61aa into Azure:main Apr 30, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants