Skip to content

Worker: maybe tidy step_id and job_id fields #1415

@josephjclark

Description

@josephjclark

Some event structures in the worker a bit confusing.

For example, on step start and complete the engine includes step_id and job_id.

But steps and jobs are synonmous!

I suspect what's happening here is that one is the UUID for the run and the other is the id or UUID of the workflow. I'd have to trace carefully through the code to see.

What I'd like to do is:

  • Establish a much clearer internal naming convention. Maybe run_step_uuid for example is a better name. Or even just step_uuid versus step_id
  • Check which field lightning actually uses and maybe only send that one

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    New Issues

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions