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

Possible breaking change about service configuration #1139

Closed
awerlang opened this issue Sep 15, 2016 · 3 comments · Fixed by #1144
Closed

Possible breaking change about service configuration #1139

awerlang opened this issue Sep 15, 2016 · 3 comments · Fixed by #1144
Assignees

Comments

@awerlang
Copy link

This used to work until 2.5.6:

AWS.config.update({dynamodb: {endpoint: '...'}});

With 2.6.2, this change was required:

AWS.config.update({dynamodb: {endpoint: '...'}}, /* allowUnknownKeys */ true);

Was this intended? It doesn't figure on CHANGELOG.

@chrisradek
Copy link
Contributor

@awerlang
Do you mean it first broke in 2.5.6? And it's fixed by setting allowUnknownKeys to true in the latest version?

@chrisradek chrisradek added the Bug label Sep 15, 2016
@chrisradek
Copy link
Contributor

@awerlang
Nevermind, I'm able to reproduce the issue you're seeing. Marking as a bug.

@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 a pull request may close this issue.

3 participants