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
CCO-392: BUGFIX Allow for Secret to exist in AWS STS case #558
Conversation
@bentito: This pull request references CCO-392 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test e2e-aws-manual-oidc |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bentito The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@bentito: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #558 +/- ##
==========================================
- Coverage 47.84% 47.82% -0.02%
==========================================
Files 93 93
Lines 11488 11501 +13
==========================================
+ Hits 5496 5500 +4
- Misses 5359 5365 +6
- Partials 633 636 +3
|
I have this in #545 - any chance we can hold this? |
/hold |
This is covered in #545. closing. |
Update Secret if it exists, or create if it doesn't.
The update part is the fix, wasn't allowing for existing Secrets before, but just creating new ones.