-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Summary
Introduce a dedicated API action for running single-image jobs that relies only on the run_single_image_ml_job permission. This avoids requiring the generic create_job permission when using the Process Now button
Detailed Description
Currently, the Process Now button triggers two actions:
create_job – creates the job object.
run_single_image_ml_job – executes the ML job on the selected image.
Since Basic Members don’t have the create_job permission by default, the request fails even though they do have run_single_image_ml_job. We resolved this in the short term by granting Basic Members the create_job permission, but this couples two actions that conceptually could be separate.
This ticket proposes adding a dedicated API action in the JobView for single-image jobs, bypassing the generic create_job check. The new action would directly rely on the run_single_image_ml_job permission. See the code for processing single images here:
Process single image function
Implementation Details
TBD
Related Issues
TBD
Additional Context
TBD