Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] broker_transport_options to support SQS attribute filter #5899

Open
4 tasks done
maratdr opened this issue Jan 3, 2020 · 1 comment
Open
4 tasks done

[Feature] broker_transport_options to support SQS attribute filter #5899

maratdr opened this issue Jan 3, 2020 · 1 comment

Comments

@maratdr
Copy link

maratdr commented Jan 3, 2020

Checklist

  • I have checked the issues list
    for similar or identical feature requests.
  • I have checked the pull requests list
    for existing proposed implementations of this feature.
  • I have checked the commit log
    to find out if the if the same feature was already implemented in the
    master branch.
  • I have included all related issues and possible duplicate issues
    in this issue (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

  • None

Possible Duplicates

  • None

Brief Summary

SQS deliever_info in the task is limited to minimum, which does not have attributes like ApproximateReceiveCount to support execution of additional logic

Design

Architectural Considerations

None

Proposed Behavior

Add a new option to app configuration
'broker_transport_options': { 'attributes_names': [ 'All' | 'VisibilityTimeout' | ... ] }
reference: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs.html#SQS.Client.receive_message

Then deliever info will provide those information.

Proposed UI/UX

Diagrams

N/A

Alternatives

None

@auvipy
Copy link
Member

auvipy commented Feb 21, 2021

contributions are wellcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants