temporalio / temporalio/api

[Feature Request] Use Payloads for ApplicationFailure message and stack trace

Open
#172 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
133
Forks
101
Avg merge
1d 22h
Merged PRs (30d)
11

Description

Is your feature request related to a problem? Please describe.

Today these fields are plain text making it possible to leak sensitive application info.

Describe the solution you'd like

Add the ability to use Payloads for these so they could be encrypted with a custom data converter

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by locating the ApplicationFailure and Payload definitions in the API sources, then trace how message and stack-trace fields are represented and how custom data converters handle Payloads. Done means both fields can use Payloads while preserving encryption through a custom data converter.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, grpc
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.