Skip to content

Fix bug that put credentials on the wrong object. #19

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

Conversation

acinader
Copy link
Contributor

@acinader acinader commented Aug 6, 2016

my $.02: this bug, though clearly my error, demonstrates why using non-standard env vars is not a good idea. In order for me to fully test, I have to unset my standard env vars:

AWS_ACCESS_KEY_ID
AWS_DEFAULT_REGION
AWS_SECRET_ACCESS_KEY

and also move my (redundant) ~/.aws config dir.

My suggestion is that this adapter should get a major revision bump that removes the paramters for access key and secret while maintaining the ability to pass them in config object. But in the case that they are passed in the config object they should have the same name that the lib expects: accessKeyId and secretAccessKey.

The two advantages of making this breaking change:

  1. promotes use of best security practices from the get go for a new user.
  2. removes an unnecessary and somewhat difficult wrinkle in testing.

@acinader
Copy link
Contributor Author

acinader commented Aug 6, 2016

@flovilmart fixes #15

@codecov-io
Copy link

Current coverage is 67.52% (diff: 100%)

No coverage report found for master at 39cacc1.

Powered by Codecov. Last update 39cacc1...3115db9

@acinader
Copy link
Contributor Author

acinader commented Aug 6, 2016

oh and 3: it would allow for a significant simplification of argument handling reducing potential bugs, increasing maintainability and readability.

@flovilmart
Copy link
Contributor

Alright, let's merge that one.

We can work on 2.0 with the breaking change. And update parse server internals / docs to reflect the breaking change. What do you think?

@flovilmart flovilmart merged commit c4561a4 into parse-community:master Aug 6, 2016
@acinader
Copy link
Contributor Author

acinader commented Aug 6, 2016

sounds good. i'll open an issue and you can assign it to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants