CLI: Update hypeman SDK to e77b77e3fe42c57676648f873cf87701d80728fa and add new commands/flags#47
CLI: Update hypeman SDK to e77b77e3fe42c57676648f873cf87701d80728fa and add new commands/flags#47kernel-internal[bot] wants to merge 2 commits intomainfrom
Conversation
Refresh the CLI to the latest hypeman-go revision after a full SDK/CLI coverage audit confirmed there are no new user-facing commands or flags to add. Made-with: Cursor
…nd add standby compression delay flags Bump the CLI to the latest hypeman-go release and wire through the new standby compression delay settings so the existing run and standby flows stay aligned with the SDK surface. Made-with: Cursor
kernel-internal
Bot
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 08a550e. Configure here.
| compression.Algorithm = parsedAlgorithm | ||
| } | ||
| params.Compression = compression | ||
| request.Compression = compression |
There was a problem hiding this comment.
Missing nested guard sends unintended compression config
Medium Severity
In lifecycle.go, the SnapshotCompressionConfigParam is unconditionally built inside the outer if block. When a user passes only --compression-delay, the compression config is still created with Enabled: true (via the fallback on line 170), even though the user never requested compression. In contrast, run.go correctly uses a nested if to guard the compression config creation, only building it when snapshot-compression-enabled, snapshot-compression-algorithm, or snapshot-compression-level is set. The lifecycle.go code is missing this same nested guard, causing unintended side effects.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 08a550e. Configure here.
This PR updates the Hypeman Go SDK to e77b77e3fe42c57676648f873cf87701d80728fa and adds CLI commands/flags for new SDK methods.
SDK Update
Coverage Analysis
This PR was generated by performing a full enumeration of SDK methods and CLI commands.
New Commands
New Flags
--compression-delayonhypeman standbyforStandbyInstanceRequestParam.CompressionDelay--snapshot-compression-delayonhypeman runforSnapshotPolicyParam.StandbyCompressionDelayTriggered by: kernel/hypeman-go@e77b77e
Reviewer: @stainless-app[bot]
Note
Medium Risk
Touches instance creation/standby request shaping and upgrades the underlying SDK, so mismatched params could change API behavior or break compression configuration, but the surface area is small and isolated to CLI flag handling.
Overview
Updates the
github.com/kernel/hypeman-godependency tov0.18.0.Extends instance standby/snapshot compression configuration to support an optional delay: adds
--compression-delaytohypeman standbyand--snapshot-compression-delaytohypeman run, and maps these flags to the new SDK request/policy fields while preserving existing compression enabled/algorithm/level behavior.Reviewed by Cursor Bugbot for commit 08a550e. Bugbot is set up for automated code reviews on this repo. Configure here.