Problem
Secrets sent by the Inngest executor in CallRequestPayload.Secrets are parsed but never exposed to functions. The SDK has a _secrets dictionary that's only populated via RegisterSecret(), but secrets from the executor are ignored.
Location: Inngest/InngestClient.cs:1110-1201 (HandleCallRequest)
The payload.Secrets field is never read or passed to InngestContext.
Expected Behavior
Functions should be able to access secrets via context.GetSecret("key") or similar API, where secrets are sourced from:
- The executor's
CallRequestPayload.Secrets
- Locally registered secrets via
RegisterSecret()
SDK Spec Reference
This blocks the SDK_SPEC "secrets" capability.
Suggested Implementation
- Add a
Secrets property to InngestContext
- Merge
payload.Secrets with locally registered secrets when building context
- Provide a
GetSecret(string key) method
Priority
Medium - required for full SDK spec compliance.
Problem
Secrets sent by the Inngest executor in
CallRequestPayload.Secretsare parsed but never exposed to functions. The SDK has a_secretsdictionary that's only populated viaRegisterSecret(), but secrets from the executor are ignored.Location:
Inngest/InngestClient.cs:1110-1201(HandleCallRequest)The
payload.Secretsfield is never read or passed toInngestContext.Expected Behavior
Functions should be able to access secrets via
context.GetSecret("key")or similar API, where secrets are sourced from:CallRequestPayload.SecretsRegisterSecret()SDK Spec Reference
This blocks the SDK_SPEC "secrets" capability.
Suggested Implementation
Secretsproperty toInngestContextpayload.Secretswith locally registered secrets when building contextGetSecret(string key)methodPriority
Medium - required for full SDK spec compliance.