feat(automation): Add KV store secret configuration#576
Open
jpshackelford wants to merge 3 commits into
Open
Conversation
Wire up AUTOMATION_KV_SECRET env var for the automation service's KV store feature. Reuses the existing jwt-secret by default to avoid requiring a new secret to be configured. The KV store provides persistent state storage for automations, allowing them to store and retrieve data across runs. Related: OpenHands/automation#67 Co-authored-by: openhands <openhands@all-hands.dev>
- Bump automation chart from 0.1.4 to 0.1.5 - Bump openhands chart from 0.4.12 to 0.4.13 - Update automation dependency version in openhands chart Co-authored-by: openhands <openhands@all-hands.dev>
all-hands-bot
approved these changes
Apr 24, 2026
Contributor
all-hands-bot
left a comment
all-hands-bot
left a comment
There was a problem hiding this comment.
Clean implementation following existing Helm chart patterns.
[RISK ASSESSMENT]
Reusing jwt-secret for both JWT signing and KV store encryption creates a shared secret between security domains. This is documented as intentional for operational simplicity. Ensure secret rotation procedures account for both use cases.
VERDICT: ✅ Worth merging
aivong-openhands
approved these changes
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Wire up
AUTOMATION_KV_SECRETenv var for the automation service's KV store feature. This reuses the existingjwt-secretby default to avoid requiring a new secret to be configured.Changes
charts/automation/templates/_env.yaml: AddAUTOMATION_KV_SECRETenv var fromkvSecretFromSecretcharts/automation/values.yaml: AddkvSecretFromSecretconfig (defaults tojwt-secret)charts/openhands/values.yaml: PasskvSecretFromSecretto automation subchartWhy reuse jwt-secret?
The KV store needs a secret for:
The existing
jwt-secrethas the same security properties (per-deployment secret used for cryptographic operations), so reusing it:openhands-secretschartRelated
This PR was created by an AI agent (OpenHands) on behalf of the user.
@jpshackelford can click here to continue refining the PR