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.

Sign up for GitHub

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

Jump to bottom

Change CLI test to use a dedicated, locked down user #3691

Open
thomas11 opened this issue Nov 7, 2024 · 0 comments
Open

Change CLI test to use a dedicated, locked down user #3691

thomas11 opened this issue Nov 7, 2024 · 0 comments
Labels
area/auth kind/enhancement Improvements or new features

Comments

@thomas11
Copy link
Contributor

thomas11 commented Nov 7, 2024

This is a follow-up to #3625. The test introduced in that issue works, but uses a real user's token which is not optimal. Ideally, we would have a dedicated artificial user for testing, whose permissions would be locked down.

The main challenge is that Azure requires 2FA.
@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Nov 7, 2024
@thomas11 thomas11 added kind/enhancement Improvements or new features area/auth and removed needs-triage Needs attention from the triage team labels Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/auth kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thomas11 @pulumi-bot