Skip to content

chore(encyclopedia): removed outdated section with old repo link #4650

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flippedcoder merged 2 commits into from
Jun 3, 2026
Merged

chore(encyclopedia): removed outdated section with old repo link #4650

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b934914
chore(encyclopedia): removed outdated section with old repo link
flippedcoder Jun 3, 2026
c027b61
Merge branch 'main' into mm/key-management-update
flippedcoder Jun 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions docs/encyclopedia/data-conversion/key-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,3 @@ It is recommended that operators estimate the encryption rate of a key and use t
Key rotation should generally be transparent to the Temporal Data Converter implementation. Temporal's `Encode()` and `Decode()` steps only need to trigger as expected, and Temporal has no knowledge of how or when you are generating your encryption keys.

You should design your Encode and Decode steps to accept all the necessary parameters for your key management, such as the key version, alongside your payloads. Like the Data Converters, keys should be mapped to a Namespace in Temporal.

### Using Vault for Key Management

[This repository](https://github.com/zboralski/codecserver) provides a robust and complete example of using Temporal with HashiCorp's [Vault](https://www.vaultproject.io/) secrets engine.