IssueTracker

What you would like to accomplish: I want to be able to specify a job name with the job creation request, rather than having the Transcoder API generate one automatically.

How this might work: We are using the Node.js client, and the v1.IJOB interface already includes a name property that is meant for created jobs. This property is ignored during job creation. I am proposing that this particular behavior change, such that we can set a value for the name property that we send in the createJob request. We would generate a UUID on our end that the Transcoder API can verify for uniqueness and reject the createJob request if there were already a job with that name.

If applicable, reasons why alternative solutions are not sufficient: The current mechanism has the API generate a UUID and return that as part of the create job response. This works but we would prefer to set our own job name because it eliminates a needless point of failure in our transcoding pipeline. We track transcoding jobs in Firestore and have to save the job name in the document in order to track its progress. If there were to be a transient error with Firestore or Cloud Functions that occurred somewhere between the job's creation and the document being updated, then the job would continue without being tracked in our database--which is very undesirable to us. There are some mechanisms that could mitigate the problem in such a scenario, such as the listJobs API, but it would be preferable to us to generate a UUID on our end and then save that to the Firestore document before creating the transcoder job instead of after.

Other information (workarounds you have tried, documentation consulted, etc): N/A