-
Notifications
You must be signed in to change notification settings - Fork 1.4k
pkg/asset/installconfig/aws: Ask for AWS access key and secret #798
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
pkg/asset/installconfig/aws: Ask for AWS access key and secret #798
Conversation
927f9d7
to
cdddb2c
Compare
The unique commit in this PR looks good to me. Waiting on #688. |
cdddb2c
to
9dec9df
Compare
9dec9df
to
3359da5
Compare
3359da5
to
4aee114
Compare
I've pushed 3359da54a -> 4aee114, rebasing onto master so GitHub just shows the one commit. |
For folks who forgot to setup ~/.aws/credentials before calling the installer. Now we'll give them a nice prompt and a link into the AWS docs instead of dying. I'm also saving any provided creds into the usual location for later AWS access during this and future installer runs. I'm constructing my own provider chain so I can drop the RemoteCredProvider which github.com/aws/aws-sdk-go/aws/defaults wants to add. I'm not entirely clear on what that's about (maybe [1]?), but it was hanging occasionally in my local testing. [1]: https://aws.amazon.com/blogs/security/how-to-eliminate-the-need-for-hardcoded-aws-credentials-in-devices-by-using-the-aws-iot-credentials-provider/
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: crawford, wking 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 |
Three e2e-aws errors:
and:
/retest |
Hrm, same failures as last time:
/retest |
/retest |
|
Here are my notes and the logs that you requested on slack: |
/retest |
Builds on #688; review that first.
For folks who forgot to setup
~/.aws/credentials
before calling the installer. Now we'll give them a nice prompt and a link into the AWS docs instead of dying. I'm also saving any provided creds into the usual location for later AWS access during this and future installer runs.