Skip to content

add process credentials provider #219

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

Merged
merged 12 commits into from
May 1, 2019
Merged

Conversation

srchase
Copy link
Contributor

@srchase srchase commented Apr 24, 2019

Description of changes:

Add process credential provider

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@srchase srchase force-pushed the process-credentials branch from 8bb3767 to 9469034 Compare April 25, 2019 21:15
@srchase srchase changed the title [WIP] Process credentials add process credentials provider Apr 25, 2019
@AllanZhengYP
Copy link
Contributor

AllanZhengYP commented Apr 29, 2019

@srchase Just a reminder: You can rebase this PR(and others) to make the checks pass.

UPDATE: the check fails because of the missing the trailing empty line in the root package.json. You can ignore it

accessKeyId,
secretAccessKey,
sessionToken
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one last comment: Do you really need the branching here? I believe the expiration is optional, so it's ok to be undefined. Just using one return will make the code cleaner

Copy link
Contributor

@AllanZhengYP AllanZhengYP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot! ship it!

@srchase srchase merged commit 406f850 into aws:master May 1, 2019
@srchase srchase deleted the process-credentials branch May 1, 2019 19:06
@lock
Copy link

lock bot commented May 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators May 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants