Skip to content

chore: Routing - In the /runs/<ID> URLs the ID should probably be a run ID, not execution ID #128

@Ark-kun

Description

@Ark-kun

The run object includes extra information like create_by, created_at and run-level annotations (that will contain information like resource requests, service account etc).

Note that we'll need deep linking capability for nested executions.

Run -> Root execution -> Child execution -> Child execution

Options:

  • /runs/{run_id}/{execution1_id}/{execution2_id}/.../{final_execution_id}
  • /runs/{run_id}/{final_execution_id}
  • /executions/{final_execution_id}

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Important issuebugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions