yourkarma / fake_sns Goto Github PK

@sborsje
Hi!

Could I ask you for audience via email or any messaging stuff?

I am contributor at yourkarma/JWT repository.
I would like to transfer yourkarma/JWT repository to different location to setup CircleCI integration.
I noticed that you merged pull request into yourkarma repository.
If you are an admin, could you add me to yourkarma admin team to transfer repository?

Thanks!

I am not sure what the scope of message delivery is, so, wanted to check. Is automatic delivery of messages to the subscribers in the scope of this project?
The (attached) sns data file shows topics, messages and subscriptions but the subscription endpoint was never called.
Thanks.

d1.txt

AWS is working on the latest version of their Ruby SDK and currently this library doesn't seem to support it.

Resolving dependencies........
Bundler could not find compatible versions for gem "aws-sdk":
  In Gemfile:
    fake_sns (>= 0) ruby depends on
      aws-sdk (~> 1.30) ruby

    aws-sdk (2.0.5.pre)

Hi,

Thanks for fake_sns, we've been using it lately for testing a number of services locally. One thing that caught us out was that messages will be repeatedly delivered on subsequent drain requests. The way we are using fake_sns is to run a thread that repeatedly drains and this was resulting in a flurry of messages being delivered to the subscribing queues.

We were thinking of something like a configuration option for only delivering messages once on drain. One approach would be to mark messages in the database once they have been delivered and then filter them in Database#each_deliverable_message.

What do you think?

I recently came across issues with SNS limits and it would be very helpful to use this lib and still be able to test agains these scenarios

Amazon SNS Limits:
http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_sns

Obscure Topic subscription limit:
https://forums.aws.amazon.com/thread.jspa?messageID=552714

The AWS SNS "subscribe" call requires a parameter with an "Endpoint" property. The AWS docs say: For the sqs protocol, the endpoint is the ARN of an Amazon SQS queue. This does not work with fake_sns.

After much trial and error I finally figured out that fake_sns accepts the name of the SQS queue as the Endpoint instead of the SQS ARN. This is a deviation from the AWS SNS API.

In order to send a message to the SQS queue fake_sns needs to have the SQS queue's URL, and AFAICT there is no reliable way to figure this out from the ARN, so this isn't something that fake_sns can "fix". However please please at least document this behavior - it took me forever to figure it out.