-
Notifications
You must be signed in to change notification settings - Fork 45
Rename AWS credentials secret data keys #164
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
Rename AWS credentials secret data keys #164
Conversation
/hold |
👍 thanks for doing this, this keeps everyone using cred secrets that I know of in sync so far. |
@spangenberg can you provide more context? Why is it needed? |
@ingvagabund Sure, the cloud credential operator has a different secret data mapping compared to the one we have. |
/retest |
/retest My only concern is whether we need backward comparability, but it's probably not a big deal at this stage. |
/hold cancel |
IINM, only our CI was consumer of the AWS secrets. Otherwise, in OpenShift it was aws instance profile that provided means to communicate with AWS service(s). |
/approve fine for me though I want another review to confirm/disprove my statement |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ingvagabund The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
/refresh |
VPC limit reached. /test e2e |
/retest |
Fixes openshift#142 Signed-off-by: Vince Prignano <[email protected]>
No description provided.