Skip to content

[Documentation] Add enum values to s3 checksum help text#10107

Open
adev-code wants to merge 1 commit intoaws:developfrom
adev-code:s3checksum_doc
Open

[Documentation] Add enum values to s3 checksum help text#10107
adev-code wants to merge 1 commit intoaws:developfrom
adev-code:s3checksum_doc

Conversation

@adev-code
Copy link
Contributor

@adev-code adev-code commented Feb 25, 2026

The help text for --checksum-mode and --checksum-algorithm in
aws s3 cp (and other s3 subcommands) did not document the accepted
enum values.

Changes

  • --checksum-mode: Added that ENABLED is the only valid value.
  • --checksum-algorithm: Added valid values
    (CRC64NVME | CRC32 | SHA256 | SHA1 | CRC32C) and default (CRC64NVME).

Testing

Screenshot 2026-02-25 at 2 32 26 PM Screenshot 2026-02-25 at 2 33 11 PM

Fixes #10025

The help text for --checksum-mode and --checksum-algorithm
did not document accepted enum values, making it unclear
what options are available without consulting external docs.

Update --checksum-mode to state ENABLED is the only valid
value. Update --checksum-algorithm to list valid values
(CRC64NVME, CRC32, SHA256, SHA1, CRC32C) and note the
default.

Fixes aws#10025
@adev-code adev-code changed the title Add enum values to s3 checksum help text [Documentation] Add enum values to s3 checksum help text Feb 25, 2026
@adev-code adev-code added the documentation This is a problem with documentation. label Feb 25, 2026
@codecov-commenter
Copy link

codecov-commenter commented Feb 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.40%. Comparing base (c4681b5) to head (b6395f4).
⚠️ Report is 150 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #10107      +/-   ##
===========================================
+ Coverage    93.39%   93.40%   +0.01%     
===========================================
  Files          210      210              
  Lines        17052    17139      +87     
===========================================
+ Hits         15925    16009      +84     
- Misses        1127     1130       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

'help_text': (
'Indicates the algorithm used to create the checksum for the object. '
'Valid values are: CRC64NVME | CRC32 | SHA256 | SHA1 | CRC32C. '
'Defaults to \'CRC64NVME\'.'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't correct for CLIv1, it uses CRC32 since CRT isn't guaranteed to be present.

Copy link
Contributor Author

@adev-code adev-code Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh ok thanks Alex. I got the information from AWS CLI S3 FAQ, it mentions info for v2:

By default, the Cyclic Redundancy Check 64 (CRC64NVME)

The CRC64NVME checksum algorithm is the default checksum algorithm used for checksum calculations.

Both of those docs does not mention v1 anywhere, I wonder if this v1 information should also be documented in the user guide and in our FAQ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like info is in V1 doc: https://docs.aws.amazon.com/cli/v1/topic/s3-faq.html#cli-aws-help-s3-faq

*By default, the Cyclic Redundancy Check 32 (CRC32) algorithm is used to calculate checksums, *

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

Successfully merging this pull request may close these issues.

aws s3 cp --checksum-mode and --checksum-algorithm enum values are not documented

3 participants