Skip to content
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

Fixes issue with service-bound global config #1144

Merged
merged 1 commit into from
Sep 20, 2016
Merged

Fixes issue with service-bound global config #1144

merged 1 commit into from
Sep 20, 2016

Conversation

chrisradek
Copy link
Contributor

Fixes issue where passing service specific configuration into AWS.config.update would silently fail by default unless allowUnknownKeys was specified.

Previously, service clients were only built when the client (i.e. AWS.S3) was accessed. Now, service clients will be built on initial load, but the api models won't be loaded until the client is instantiated.

Fixes #1139

//cc: @LiuJoyceC

…fig.update would silently fail by default unless allowUnknownKeys was specified.

Fixes #1139
@coveralls
Copy link

coveralls commented Sep 16, 2016

Coverage Status

Coverage decreased (-2.4%) to 87.828% when pulling 662dd3d on chrisradek:fix-service-config into 5a26680 on aws:master.

@LiuJoyceC
Copy link
Contributor

I like these changes. In addition to fixing the bug, it also now lazy loads service API models even when you directly require an individual service, which is consistent with how it was done before version 2.6.0, and consistent with how models are loaded when all services are required. Even better, now it only loads the model for a specific version.

🚀

@chrisradek chrisradek merged commit 044597b into aws:master Sep 20, 2016
chrisradek added a commit that referenced this pull request Sep 20, 2016
@lock
Copy link

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

Possible breaking change about service configuration
4 participants