Describe the Feature
I've found local debugging of AWS Lambdas combined with SQS to be a real pain.
It would be great if the Mock Lambda Test Tool had the ability to connect to a remote AWS SQS queue and respond to events. I know there are some sample messages available from the main testing page, but using an actual queue would be great.
The "Dead Letter Queue" functionality of the tool seems like it is basically doing that. However, I want to respond to a non-dead letter queue.
Is your Feature Request related to a problem?
No issue with the tool, per se.
Proposed Solution
N/A
Describe alternatives you've considered
I've tried using LocalStack, which is just pretty painful to use when it comes to fast iteration development using .NET.
Additional Context
Here's a scenario:
- Launch the Mock Lambda Test Tool
- Go to some new feature that allows you to select an SQS queue, reading from your local AWS profile (like the Dead Letter Queue page)
- Go to the AWS Console, or use the AWS CLI, and start pumping a lot of events into the queue. This would help me debug and troubleshoot more than just one event at a time.
Environment
N/A
This is a 🚀 Feature Request
Describe the Feature
I've found local debugging of AWS Lambdas combined with SQS to be a real pain.
It would be great if the Mock Lambda Test Tool had the ability to connect to a remote AWS SQS queue and respond to events. I know there are some sample messages available from the main testing page, but using an actual queue would be great.
The "Dead Letter Queue" functionality of the tool seems like it is basically doing that. However, I want to respond to a non-dead letter queue.
Is your Feature Request related to a problem?
No issue with the tool, per se.
Proposed Solution
N/A
Describe alternatives you've considered
I've tried using LocalStack, which is just pretty painful to use when it comes to fast iteration development using .NET.
Additional Context
Here's a scenario:
Environment
N/A
This is a 🚀 Feature Request