This feature is in preview. The API may change before general availability. To try it out, contact support@intunedhq.com and we’ll enable it for your workspace.
ephemeral_parameters. Unlike parameters, ephemeral parameters are never stored on the Run record, never sent to sinks, and never appear in logs or traces. They exist only for the lifetime of the Run.
Use them for a secret that belongs to a single Run—a portal password supplied by an end user, a one-time code, or a government ID you must not retain.
Available helpers
get_ephemeral_parameter— Read an ephemeral parameterinvalidate_ephemeral_parameter— Delete an ephemeral parameter
Function reference
get_ephemeral_parameter
None if the key wasn’t passed to the Run, or if it has already been invalidated.
Parameters
The top-level key of the ephemeral parameter, as passed in the Run’s
ephemeral_parameters map.None if it isn’t available. Values are JSON scalars—str, int, float, or bool.
Raises
- An exception if the Run is traced and no
without_tracingblock is open. - An exception if the value can’t be read, for example when the machine running the Run doesn’t answer in time. The message names the key, never the value.
invalidate_ephemeral_parameter
None.
Invalidation and retries
Ephemeral parameters are stored per Run and shared by every attempt of that Run. That makes invalidation a tradeoff:- Invalidate early and the value is gone the moment you’re done with it—but a retry can no longer read it, so the retry fails.
- Don’t invalidate and every attempt can read the value. It’s still deleted automatically when the Run reaches a terminal state, or by its 24-hour TTL if the Run never starts.
Related
- Ephemeral parameters — Passing them to a Run, storage, and lifetime.
- Pause tracing — Control what gets recorded around a sensitive step.
- Environment variables and secrets — For secrets that are the same on every Run.
- Non-retryable errors — Stop a Run that can’t succeed without new input.