Allow user-defined container names with runtime expressions in `run` container tasks

[JBBianchi]

What would you like to be added?

I propose enabling users to define container names dynamically using runtime expressions in run container tasks.

Proposal(s):

Currently, when executing a run task of type container, there is no way to specify a custom container name dynamically based on runtime information. I propose extending the specification to allow a name field in the container definition that supports runtime expressions.

For example:

do:
  - runContainer:
      run:
        container:
          name: ${ "fake-\(.workflow.id)-\(.task.id)" }
          image: fake-image

Here, the name field would accept runtime expressions, enabling users to create container names dynamically using workflow and task metadata, such as workflow.id, task.id, or other relevant properties.

Alternative(s):

No response

Additional info:

• Allowing runtime expressions in container names would provide greater flexibility and control to users, improving the observability and traceability of workflows.
• This feature could be optional, ensuring backward compatibility with existing implementations.
• Potential use cases include aligning container names with specific organizational or operational conventions, facilitating streamlined debugging and monitoring.

Community Notes

• Please vote by adding a 👍 reaction to the feature to help us prioritize.
• If you are interested to work on this feature, please leave a comment.