Skip to content

SQS Checksum Validation #222

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.

Sign up for GitHub

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

Jump to bottom
Open
kggilmer opened this issue Mar 4, 2021 · 5 comments
Open

SQS Checksum Validation #222

kggilmer opened this issue Mar 4, 2021 · 5 comments
Labels
customization Service Customization feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed. p2 This is a standard priority issue post-dp Not likely in scope until after Dev Preview

Comments

@kggilmer
Copy link
Contributor

kggilmer commented Mar 4, 2021

Can be disabled with DisableComputeChecksums. This may be modeled now?

internal id: 176558055
@vinoddin
Copy link

Per trigage on 5/12, need an SME to weigh in on the value of this feature. Found only refs to bugs on Go.

@kggilmer
Copy link
Contributor Author

I don't see anything about this in the SEP repo. I don't see anything via search is.amazon.com, and I don't see anything about it in the Go v2 or Java SDKs.

I've searched the public docs of SQS for mention of being able to disable checksums and came up with nothing. This page references checksums only to say that they are calculated by the SDK. No mention of disabling or configuring the feature.

@aajtodd aajtodd transferred this issue from smithy-lang/smithy-kotlin Jul 8, 2021
@aajtodd aajtodd added customization Service Customization post-dp Not likely in scope until after Dev Preview labels Jul 8, 2021
@kneekey23 kneekey23 mentioned this issue Aug 20, 2021
Open
@github-actions
Copy link

github-actions bot commented Jul 8, 2022

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to provide a comment or open a new issue.

@github-actions github-actions bot added closing-soon This issue will automatically close in 2 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 2 days unless further comments are made. labels Jul 8, 2022
@ianbotsf ianbotsf added no-auto-closure We do not want this issue to be automatically closed. and removed closed-for-staleness labels Jul 11, 2022
@ianbotsf ianbotsf reopened this Jul 11, 2022
@ianbotsf
Copy link
Contributor

See SQS documentation for more details on checksums.

@RanVaknin RanVaknin added feature-request A feature should be added or improved. p2 This is a standard priority issue labels Nov 27, 2024
@lauzadis
Copy link
Member

Implemented by @xinsong-cui in smithy-lang/smithy-kotlin#1253 and #1544. Pending internal specification to be written / reviewed / approved before we release our implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customization Service Customization feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed. p2 This is a standard priority issue post-dp Not likely in scope until after Dev Preview
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@aajtodd @lauzadis @vinoddin @RanVaknin @kggilmer @ianbotsf