User defined job identifier

[wdbaruni]

The Problem

Users today only interact with bacalhau user system generated job IDs, which is not a great user experience specially when working with long running jobs. It has been a pain working on the use cases where I can to stop and deploy a new version of the job, and each time had to figure out the new ID for my job.

Similar systems allow users to generate their own names for their jobs, which simplifies querying the jobs, updating them and stopping the jobs if needed.

Requirements

1. As a user, I prefer to submit and query jobs using a unique job name I provide, rather than relying solely on a Bacalhau-generated job ID.
2. As a user, I want to stop a job using the unique name I have provided, in addition to the Bacalhau-generated ID.
3. As a user, I expect re-submitting a job with the same name to be treated as an update by Bacalhau, triggering appropriate actions.
4. As a user, I want re-submitting a job with the same specifications and name to result in no action from Bacalhau and no increment to the job version

This feature is a pre-requirement to Users shall be able to update existing jobs

Priority

• Priority: 2 (Medium)
• Quarter: 2024Q2
• Justification:
  • I am on the fence of marking this as high, but there are other higher priority items and this is mainly impacting long running jobs which doesn't seem to be getting a lot of demand yet

[wdbaruni]

replaced by linear project