-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: bump deps and get rid of github.com/Azure/azure-service-bus-go #3639
Conversation
/run-e2e |
/run-e2e workload_identity* |
please @v-shenoy , take a look to servicebus part. I had to reimplement part of it during the dep migration. |
Even snyk reports a new vulnerability introduced, I think it's a false detection because we already use the fixed version in this PR: It's seems like the issue about restful dep we talked about some week ago |
/run-e2e |
/run-e2e service_bus |
I'm checking the e2e tests, I'd say that the error is in the e2e test itself. 👀 |
/run-e2e service_bus* |
/run-e2e workload_identity* |
On a related note, could you move the utility functions used in the service bus tests (setting/ cleaning up queue / topic / subscription, etc) into a separate package so that we can reuse them? If not here, I'll try to do them as a part of #3607 |
I'll try it |
/run-e2e workload_identity* |
/run-e2e |
/run-e2e workload_identity* |
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.
LGTM. The only scenario that concerns me is pod identity, wish there was a way we could check it easily right now, considering we lack e2e tests.
I'll spawn aad-pod-identity on my cluster and try it, but it's true, having aad-pod-identity e2e test would be nice. |
/run-e2e azure* |
I have tried in my cluster with aad-pod-identity and it works. I have followed this doc to configure aad-pod-identity using the addon, and it has been really easy. Covering the case with a test is also easy because we only need to copy-paste the workload-identity e2e test and change the trigger authentication from |
Once this is merged, I can tackle the feature request for SAS strings as we'll have the new SDK in use. |
/run-e2e workload_identity* |
/run-e2e azure* |
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
6b52397
to
ad919c6
Compare
/run-e2e workload_identity* |
Signed-off-by: Jorge Turrado jorge_turrado@hotmail.es
Checklist
Fixes #3394
Fixes #2986
Related to kedacore/keda-docs#930