-
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
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 |
dc06dde
to
1e6115b
Compare
Unit tests are passing now |
Signed-off-by: Maksymilian Boguń <[email protected]>
675b2dd
to
d536acb
Compare
/run-e2e aws |
Signed-off-by: Maksymilian Boguń <[email protected]>
Can we merge the PR? I'd rather not be stuck in the conflict -> merge -> e2e test -> conflict death spiral ;) |
it seems e2e tests got stuck again? otherwise can you merge this pr @zroubalik, please? |
@zroubalik @wozniakjan , PTAL |
Signed-off-by: Maksymilian Boguń <[email protected]>
@JorTurFer @zroubalik Please take a look at this PR. It's waiting for approval for 3 weeks now. The change is ready, waiting to be merged. |
@maxbog there are some conflicts, please fix them and then I think we can merge this. |
Signed-off-by: Maksymilian Boguń <[email protected]>
@zroubalik done, no conflicts now |
Signed-off-by: Maksymilian Boguń <[email protected]>
Can we force this through, can the e2e testing either be removed or ignored? |
/run-e2e aws |
* Introduce aws region into the AWS config cache Signed-off-by: Maksymilian Boguń <[email protected]> * add CHANGELOG entry Signed-off-by: Maksymilian Boguń <[email protected]> * embedded AWS region into Authorization metadata Signed-off-by: Maksymilian Boguń <[email protected]> * move the fix to Unreleased version Signed-off-by: Maksymilian Boguń <[email protected]> * Fix indentation Signed-off-by: Maksymilian Boguń <[email protected]> --------- Signed-off-by: Maksymilian Boguń <[email protected]> Signed-off-by: Jan Wozniak <[email protected]> Co-authored-by: Jorge Turrado Ferrero <[email protected]> Co-authored-by: Jan Wozniak <[email protected]>
* Introduce aws region into the AWS config cache Signed-off-by: Maksymilian Boguń <[email protected]> * add CHANGELOG entry Signed-off-by: Maksymilian Boguń <[email protected]> * embedded AWS region into Authorization metadata Signed-off-by: Maksymilian Boguń <[email protected]> * move the fix to Unreleased version Signed-off-by: Maksymilian Boguń <[email protected]> * Fix indentation Signed-off-by: Maksymilian Boguń <[email protected]> --------- Signed-off-by: Maksymilian Boguń <[email protected]> Signed-off-by: Jan Wozniak <[email protected]> Co-authored-by: Jorge Turrado Ferrero <[email protected]> Co-authored-by: Jan Wozniak <[email protected]>
Just confirming, was this change included in the 2.16.1 release? |
No, we don't include a new features in the patch releases. This will be included in 2.17. |
I would argue this is a fix and not a feature given that it's being implemented to account for a bug in handling cached credentials when the next target in an aws environment is in a different region. Are there any ETA's or target dates for 2.17? Edit: Just read the roadmap, apologies on the question above haha |
* Introduce aws region into the AWS config cache Signed-off-by: Maksymilian Boguń <[email protected]> * add CHANGELOG entry Signed-off-by: Maksymilian Boguń <[email protected]> * embedded AWS region into Authorization metadata Signed-off-by: Maksymilian Boguń <[email protected]> * move the fix to Unreleased version Signed-off-by: Maksymilian Boguń <[email protected]> * Fix indentation Signed-off-by: Maksymilian Boguń <[email protected]> --------- Signed-off-by: Maksymilian Boguń <[email protected]> Signed-off-by: Jan Wozniak <[email protected]> Co-authored-by: Jorge Turrado Ferrero <[email protected]> Co-authored-by: Jan Wozniak <[email protected]> Signed-off-by: Chirag Bhatia <[email protected]>
The PR adds the AWS region to the key used by the AWS config cache
Checklist
Fixes #6128