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

[BREAKING] Make region a required configuration. #31

Merged
merged 1 commit into from
Dec 16, 2015

Conversation

LevelbossMike
Copy link
Member

region is now a required configuration option which is
the same behaviour as in the ember-cli-deploy-s3-plugin.
This will break deploys that rely on the default region of
us-east-1 but will fail with a useful error message.

Closes #30

`region` is now a required configuration option which is
the same behaviour as in the `ember-cli-deploy-s3`-plugin.
This will break deploys that rely on the default region of
`us-east-1` but will fail with a useful error message.

Closes ember-cli-deploy#30
achambers pushed a commit that referenced this pull request Dec 16, 2015
[BREAKING] Make `region` a required configuration.
@achambers achambers merged commit c66374a into ember-cli-deploy:master Dec 16, 2015
@achambers
Copy link
Member

👍

@lukemelia
Copy link
Contributor

I'm sure I'm just being dense, but where is region actually used in the codebase?

@achambers
Copy link
Member

@lukemelia I think you'll find it's here -> https://github.com/ember-cli-deploy/ember-cli-deploy-s3-index/blob/master/lib/s3.js#L27-L30

The config options are just passed straight through to the AWS.S3 client.

@lukemelia
Copy link
Contributor

Ah, OK. Seems like that is a lot of unintentional API surface area.

@LevelbossMike
Copy link
Member Author

mmh. That was actually meant as a way for 'power users' to be able to customize the S3 client. Which might be kind of useless because the other s3 plugin is not providing that option and it now seems more like a YAGNI thing when thinking about it ;)

The only thing the other plugins are passing to the S3 client is region and the accessKey stuff correct?

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