[GH-ISSUE #82] Expose boto3, botocore git commit + data hash information as part of `--version` output #148

New issue

Closed

opened 2026-03-15 11:47:36 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 11:47:36 +03:00

Owner

Originally created by @hwei0 on GitHub (Dec 15, 2025).
Original GitHub issue: https://github.com/awslabs/iam-policy-autopilot/issues/82

During build.rs stage:

Get the git commit hash and tag (if present) for each of boto3 and botocore submodules
Compute a hash over all the simplified files in boto3-data-simplified and botocore-data-simplified
Write to a intermediate file, all this info for each of boto3, botocore

In CLI, upon a call to --version:

Read the respective intermediate file, retrieve the commit hash, git tag, and data hash
Output to command line the following, in addition to existing version information: {boto3/botocore} version: commit={commit_hash}, tag={tag if tag is present else None}, data_hash={data_hash}

Originally created by @hwei0 on GitHub (Dec 15, 2025). Original GitHub issue: https://github.com/awslabs/iam-policy-autopilot/issues/82 During `build.rs` stage: - Get the git commit hash and tag (if present) for each of `boto3` and `botocore` submodules - Compute a hash over all the simplified files in `boto3-data-simplified` and `botocore-data-simplified` - Write to a intermediate file, all this info for each of `boto3`, `botocore` In CLI, upon a call to `--version`: - Read the respective intermediate file, retrieve the commit hash, git tag, and data hash - Output to command line the following, in addition to existing version information: `{boto3/botocore} version: commit={commit_hash}, tag={tag if tag is present else None}, data_hash={data_hash}`

kerem closed this issue

2026-03-15 11:47:41 +03:00

kerem commented

2026-03-15 11:47:47 +03:00

Author

Owner

@adpaco-aws commented on GitHub (Dec 15, 2025):

Instead of separate version commands for these, I'd recommend printing the information as part of --version (I believe the version command behavior can be overriden in clap).

@adpaco-aws commented on GitHub (Dec 15, 2025): Instead of separate version commands for these, I'd recommend printing the information as part of `--version` (I believe the version command behavior can be overriden in `clap`).

kerem commented

2026-03-15 11:47:52 +03:00

Author

Owner

@weibenz1 commented on GitHub (Dec 15, 2025):

tag={tag if tag is present else None}

I thought we'd always be monitoring tags rather than latest commit - in this case when would we not have it?

@weibenz1 commented on GitHub (Dec 15, 2025): > tag={tag if tag is present else None} I thought we'd always be monitoring tags rather than latest commit - in this case when would we not have it?

kerem commented

2026-03-15 11:47:57 +03:00

Author

Owner

@hwei0 commented on GitHub (Dec 15, 2025):

When I pulled and submodule updated a few hours ago, there werent any tags with that commit it seemed

@hwei0 commented on GitHub (Dec 15, 2025): When I pulled and submodule updated a few hours ago, there werent any tags with that commit it seemed

kerem referenced this issue

2026-03-15 11:50:43 +03:00

[GH-ISSUE #146] Fix weekly submodule Github Action #127

kerem referenced this issue

2026-03-15 11:56:23 +03:00

[PR #148] [MERGED] ci: create signed commit from github actions for weekly submodule updates #260