Skip to content

Add $runtime argument for implementation specific information #950

Closed
@matthias-pichler

Description

@matthias-pichler

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 inside run.container tasks

Why is this needed:

See #932

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: specChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version change

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions