Feature Request: Start and stop poller?

[ashovlin]

Describe the feature

A potential user reached out internally, looking to pause/resume message handling.

Our mindset when developing this was that the message pump would run for the whole lifecycle of the application as a BackgroundService that would be started by the host.

Use Case

They use case is for a blue/green deployment where they would just like the active slice to be processing messages.

Proposed Solution

We do have some spots in our test code where we're starting at stopping it at will, but I think we'd have to flip the visibility of MessagePumpService from internal to public before users could do something similar.

https://github.com/awslabs/aws-dotnet-messaging/blob/ee29c3dadeaf7c49116727db1d2cf[…]2b9ad853a/test/AWS.Messaging.UnitTests/SQSMessagePollerTests.cs

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS.Messaging (or related) package versions

N/A

Targeted .NET Platform

N/A

Operating System and version

N/A

[jkwpappin]

Hi. I have raised a PR for this issue.
Tested via Unit tests. I have an integration test as well but wasn't able to run them locally.
I exposed a configuration item, PollingControlToken, that can be used to start/stop message receipt, so that the BackgroundService (MessagePumpService) can remain unmodified.