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

Add e2e test for Azure Monitor using Workload Identity and Pod Identity #3887

Closed
Tracked by #2357 ...
JorTurFer opened this issue Nov 22, 2022 · 0 comments · Fixed by #4200
Closed
Tracked by #2357 ...

Add e2e test for Azure Monitor using Workload Identity and Pod Identity #3887

JorTurFer opened this issue Nov 22, 2022 · 0 comments · Fixed by #4200
Labels
good first issue Good for newcomers help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing

Comments

@JorTurFer
Copy link
Member

Proposal

We need to add e2e test coverage for the scenario

Use-Case

No response

Anything else?

No response

@JorTurFer JorTurFer added help wanted Looking for support from community testing stale-bot-ignore All issues that should not be automatically closed by our stale bot labels Nov 22, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Nov 22, 2022
@JorTurFer JorTurFer added the good first issue Good for newcomers label Dec 9, 2022
@JorTurFer JorTurFer changed the title Add e2e test for Azure Monitor using Workload Identity Add e2e test for Azure Monitor using Workload Identity and Pod Identity Jan 23, 2023
@github-project-automation github-project-automation bot moved this from Proposed to Ready To Ship in Roadmap - KEDA Core Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant