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

Include imitation of 10 message attributes field for sns.PublishInput in godoc #2608

Closed
rengas opened this issue Apr 16, 2024 · 2 comments
Closed
Assignees
Labels
documentation This is a problem with documentation.

Comments

@rengas
Copy link

rengas commented Apr 16, 2024

Describe the issue

From the docs I quote

Amazon SNS supports delivery of message attributes, which let you provide structured metadata items (such as timestamps, geospatial data, signatures, and identifiers) about the message. For SQS subscriptions, a maximum of 10 message attributes can be sent when Raw Message Delivery is enabled. To send more than 10 message attributes, Raw Message Delivery must be disabled. Messages with more than 10 message attributes directed towards Raw Message Delivery enabled Amazon SQS subscriptions will be discarded as client side errors.

Please consider adding this limitation to godoc of sns.PublishInput or at least the link should be added

Links

https://docs.aws.amazon.com/sns/latest/dg/sns-message-attributes.html

AWS Go SDK V2 Module Versions Used

github.com/aws/aws-sdk-go-v2 v1.21.0

@rengas rengas added documentation This is a problem with documentation. needs-triage This issue or PR still needs to be triaged. labels Apr 16, 2024
@RanVaknin
Copy link
Contributor

Hi @rengas ,

Thanks for reaching out. What you are asking for makes sense, but the SDK docs are code generated from the API models of each AWS service. Because of that, the SDK team cannot change / add / remove documentation from service or operation specific constructs.
Instead, You can submit feedback directly to the service team by pressing on the Feedback button found on the top right corner of every API reference page.

Since this is not actionable by the SDK team, Im going to go ahead and close this issue.
Thanks again for taking the time and submitting the request.

All the best,
Ran~

@RanVaknin RanVaknin self-assigned this Apr 18, 2024
@RanVaknin RanVaknin removed the needs-triage This issue or PR still needs to be triaged. label Apr 18, 2024
@RanVaknin RanVaknin closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is a problem with documentation.
Projects
None yet
Development

No branches or pull requests

2 participants