Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Amazon SQS Scope Changes / Fixes

See original GitHub issue

I’m configuring amazon sqs host like below, At the description of Scope it is written that this will be used as a prefix for queues and topics. But when I look to the aws console I don’t see any prefixes in the queues and topics. My intention was to use it for creating different environments for queues so when e.g. I publish something in development it will not be consumed in Prod

x.Host(new Uri($"amazonsqs://{_config.Region}/"), h => { h.AccessKey(_config.AccessKey); h.SecretKey(_config.SecretKey); h.Scope(_config.Environment); });

Issue Analytics

State:
Created 3 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

phatboygcommented, May 6, 2020

Okay, that settles it. @Crozin you were the one I was most concerned about, and if you’re still fighting with it, it’s settled.

And I think I’ll make topics scoped by default as well. It’s a one-time breakage that actually fixes itself once services are upgraded.

0reactions

danportscommented, Nov 15, 2020

Makes sense. Agreed - the docs have great complete working examples but as soon as I need to deviate from them a little bit I find myself doing a lot of googling/code spelunking to trying to piece together the solution.