Skip to content

Widen region option in SignatureV4 ctor to accept a region provider and move credentials to be a ctor argument #44

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 1 commit into from
Aug 26, 2017

Conversation

jeskew
Copy link
Contributor

@jeskew jeskew commented Aug 17, 2017

This change makes credentials and region required constructor arguments for the SignatureV4 signer class but allows users to pass in asynchronous providers instead of a string or object literal. region was previously required but had to be a string, and credentials was previously a required parameter when calling the SignatureV4::presignRequest or SignatureV4::signRequest.

Making this change simplifies the calling pattern customers will need to follow to sign requests. They can pass a credential provider to the object's constructor and then invoke signRequest with just a request object.

@AllanZhengYP
Copy link
Contributor

looks good.

@jeskew jeskew merged commit 17cfb12 into aws:master Aug 26, 2017
@jeskew jeskew deleted the fix/v4-signer-tweaks branch August 26, 2017 01:23
trivikr referenced this pull request in trivikr/aws-sdk-js-v3 Dec 10, 2018
Widen region option in SignatureV4 ctor to accept a region provider and move credentials to be a ctor argument
@lock
Copy link

lock bot commented Sep 26, 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 Sep 26, 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.

3 participants