Skip to content

feat: job decrypt#123

Draft
schitizsharma wants to merge 2 commits intostagingfrom
feat/job-decrypt
Draft

feat: job decrypt#123
schitizsharma wants to merge 2 commits intostagingfrom
feat/job-decrypt

Conversation

@schitizsharma
Copy link
Copy Markdown
Collaborator

Description

This PR adds decryption support to the olake-worker to 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:

  • New Utility: Created worker/utils/encryption.go to handle decryption using a key derived from the OLAKE_SECRET_KEY environment variable.
  • Support for Multiple Modes: Implement both Local AES-256-GCM and AWS KMS decryption modes (triggered if the secret key is an ARN).
  • Core Update: Updated worker/database/job.go to automatically decrypt Source and Destination configs during GetJobData.
  • Dependencies: Added AWS SDK v2 dependencies to worker/go.mod.

Fixes # (issue)

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

  • Build Verification: Ran go build ./... in the worker directory to confirm all dependencies are correctly resolved.
  • Code Review: Verified that the AES-GCM and KMS decryption flow matches the implementation in olake-ui/server/utils/encryption.go.

Screenshots or Recordings

N/A (Backend logic change)

Related PR's (If Any):

N/A

chore: staging -> master (olake-worker v0.3.3 , helm v0.0.14)
@schitizsharma schitizsharma changed the title Feat/job decrypt feat: job decrypt Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant