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
Added support for workload identity #2619
base: main
Are you sure you want to change the base?
Conversation
gapra-msft
commented
Mar 21, 2024
•
edited
edited
- Marks the servicePrincipal and identity flags as soon to be deprecated. This is replaced by login-type.
- Currently we have custom workload identity flags/env variables, but to me it seems reasonable to just rely on the default of the environment variables the Identity SDK uses, this would reduce our test burden.
func (s *WorkloadIdentitySuite) Scenario_SingleFileUploadDownloadWorkloadIdentity(svm *ScenarioVariationManager) { | ||
// Run only in environments that support and are set up for Workload Identity (ex: Azure Pipeline, Azure Kubernetes Service) | ||
if os.Getenv("NEW_E2E_ENVIRONMENT") != "AzurePipeline" { | ||
svm.InvalidateScenario() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: logging skips may be a good idea-- But there's no proper mechanism for this at the moment.
InvalidateScenario was intended to basically be "in no context does this scenario ever make sense, or should it ever exist", like local to local.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add a svm.Skip thing and enhance the e2e framework then.