[Feature Request] Use Payloads for ApplicationFailure message and stack trace
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
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.
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
- Dominant language
- Go
- Stars
- 133
- Forks
- 101
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from temporalio/api
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
temporalio/api#750 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#427 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
temporalio/api#421 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#400 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
temporalio/api#328 · 6 reactions ·
Similar issues
-
cvss-severity:high devguard l3montree-cybersecurity/devguard/devguard pkg:golang/github.com/l3montree-dev/devguard risk:low state:open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
l3montree-dev/devguard#3146 · 1 comment ·
Maintainers usually reply within 1 day
-
CLI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
databricks/cli#6910 ·
Maintainers usually reply within 1 day
-
Table presenter appends a spurious ", ..." to the FIX column when all fix versions are already shownOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
canonical/microceph#900 · 1 comment ·
Maintainers usually reply within 1 day
-
vulncheck or vulndb
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day