feat: job decrypt#123
Merged
Merged
Conversation
Decrypt AES-256-GCM (local) and AWS KMS encrypted configs stored in the database before passing them to job execution. If OLAKE_SECRET_KEY is not set, configs are used as-is. Co-authored-by: Cursor <cursoragent@cursor.com>
vikaxsh
approved these changes
May 19, 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
2 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.
Description
This PR adds decryption support to the
olake-workerto ensure that encrypted source and destination configurations can be read from the database. The implementation mirrors the server-side decryption logic, allowing for seamless communication between the UI/Server and the Worker.Key Changes:
worker/utils/encryption.goto handle decryption using a key derived from theOLAKE_SECRET_KEYenvironment variable.worker/database/job.goto automatically decryptSourceandDestinationconfigs duringGetJobData.worker/go.mod.Fixes # (issue)
Type of change
How Has This Been Tested?
go build ./...in the worker directory to confirm all dependencies are correctly resolved.olake-ui/server/utils/encryption.go.Screenshots or Recordings
N/A (Backend logic change)
Related PR's (If Any):
N/A