-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Remove Aws.config #293
Comments
@mariokostelac WDYT? This should be part of the next version 3.0.0, all together with #291. If ok with that and if you have a spare time, could you work on that? |
@phstc give me few days to take a look, probably end of the week. |
I have most of my AWS resources in a different region from my SQS queues, since amazon only supports FIFO in a few regions. If you go this way, please provide a way to override region ONLY for shoryuken :) |
@mbriggs would |
yeah, totally :) just need some kind of way to configure stuff outside of the global sdk configuration |
We should drop any AWS credentials setup from Shoryuken, like this:
In favor of leveraging
Aws.config
.aws-sdk is very powerful and supports a few different ways to configure it, we shouldn't duplicate this logic in Shoryuken. This would also "resolve" the problem about people complaining that they've configured the creds in
shoryuken.yml
, but it isn't picked up in client mode (Rails), they would know that they need to configure that by themselves.Aws.config
The maximum we can provide is a setter
sqs=
to allow people to set the SQS Client, in case the have a specific need, such assqs_endpoint
or they want to have different credentials other than the ones inAws.config
. I'm not totally convinced about this setter yet, but that is the maximum we can provide.We currently support
receive_message
in theshoryuken.yml
, but I think people only use it to for attributes, and because of the FIFO queue, we ask for all by default.The text was updated successfully, but these errors were encountered: