-
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
Add AWS region to the AWS Config Cache key #6134
base: main
Are you sure you want to change the base?
Conversation
e025102
to
a67350c
Compare
a67350c
to
569eeb9
Compare
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.
The build is broken
Signed-off-by: Maksymilian Boguń <[email protected]>
569eeb9
to
8e5b30f
Compare
Signed-off-by: Maksymilian Boguń <[email protected]>
8e5b30f
to
baa3cc1
Compare
@zroubalik I fixed the build |
/run-e2e aws |
/run-e2e aws |
@zroubalik Is something wrong with the e2e tests? I see they failed twice now :( |
yeah, issue on our side, will rerun once it is fixed |
@zroubalik any updates on the e2e testing? |
/run-e2e aws |
Signed-off-by: Maksymilian Boguń <[email protected]>
@JorTurFer I rebased the PR |
/run-e2e aws |
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.
PTAL @kedacore/keda-core-contributors
Any insight into why it paniced/failed on the amd64 validation? |
@JorTurFer is the validate - amd64 stage failure an issue with the action or an issue with the code changes in this pr? |
I've triggered it again because probably it was a transient error |
@zroubalik @wozniakjan PTAL |
/run-e2e aws |
The PR adds the AWS region to the key used by the AWS config cache
Checklist
Fixes #6128