-
Couldn't load subscription status.
- Fork 166
Closed
Labels
area: specChanges in the SpecificationChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version changeNew feature or request. Impacts in a minor version change
Milestone
Description
What would you like to be added:
As discussed in #932 we will introduce a new runtime expression argument called $runtime that holds implementation specific information. It will include the following standard fields for now:
$runtime.name... the name of the runtime (e.g. Synapse, Sonanta, ...)$runtime.version... the version of the runtime (e.g. commit sha, image hash, (semantic) version, ...)$runtime.metadata... custom values that be set by implementors (e.g. tenantId, account, ...) alternatively we could use$runtime.implementation?
Future Additions
The following fields can be added in the future but haven't been decided yet:
Current Time
$runtime.now.iso8601$runtime.now.epochMillis$runtime.now.epochNanos
Execution start times
An alternative proposed by @cdavernas was $workflow.startedAt ... which I prefer and propose in #951
$runtime.executionStart.iso8601$runtime.executionStart.epochMillis$runtime.executionStart.epochNanos
Task start times
An alternative proposed by @cdavernas was $task.startedAt ... which I prefer and propose in #951
$runtime.taskStart.iso8601$runtime.taskStart.epochMillis$runtime.taskStart.epochNanos
Operating System (suggested by @fjtirado )
$runtime.os... Personally not a fan because it might not always make sense/be known and might have unclear semantics insiderun.containertasks
Why is this needed:
See #932
Metadata
Metadata
Assignees
Labels
area: specChanges in the SpecificationChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version changeNew feature or request. Impacts in a minor version change
Type
Projects
Status
Done