fix(sdk): aws queue client does not delete popped messages

[flyingImer]

Checklist

• Title matches Winglang's style guide
• Description explains motivation and solution
• Tests added (always)
• Docs updated (only required for features)
• Added pr/e2e-full label if this feature requires end-to-end testing

By submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.

[Chriscbr]

LGTM

In the future I wonder if we should rework the Queue API to give the user a bit more control -- e.g. pop could return you a Task object that can be deleted from the queue with task.complete()

[tsuf239]

Tests are passing!

[flyingImer]

LGTM

In the future I wonder if we should rework the Queue API to give the user a bit more control -- e.g. pop could return you a Task object that can be deleted from the queue with task.complete()

I actually had a couple of POCs on that track, but ended up dropping them. I think the current queue API is closer to the classic data structure interface, so I pivoted to match the simulator behavior.

However, I definitely agree with you on the user control story, especially after seeing messages like "queue is not FIFO" in the code base. Queue API might need to re-position itself a bit between classic queue surface and its characteristic of being distributed in the cloud.

[Chriscbr]

Ran the queue tests again, all passed 👍

[mergify]

Thanks for contributing, @flyingImer! This PR will now be added to the merge queue, or immediately merged if fix-queue-pop-iii is up-to-date with main and the queue is empty.

[monadabot]

Congrats! 🚀 This was released in Wing 0.33.24.