temporalio / temporalio/features
[Feature Request] Allow running failure fields through codec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Failure fields may have sensitive info, including message, stack_trace, and details, and maybe type.
Most of this would require changing the fields to Payloads. Currently only details like:
are converted to Payloads, and in TS SDK, it isn't put through codecs.
Describe the solution you'd like
Provide a way for them to be run through an encryption codec.
Checklist:
- API change
- Release a compatible server - server must add to list of capabilities
- Go SDK
- TS SDK
- Java SDK
- Python SDK
- PHP SDK
- Ruby SDK
- Feature test in this repo
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with temporal/api/failure/v1/message.proto at the referenced failure fields and review the completed SDK checklist to identify what remains. Inspect the feature-test area in this repository and the PHP SDK integration; done means failure fields can run through the encryption codec and the feature test is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, ruby, typescript
- Domain
- backend-api-design, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100