Structure of "job" JSON

I understand that at the very least there is

job["id"]

job["id"]

and

job["input"]

job["input"]

and we utilize it.
It will help me a great deal if I could send additional information like

job["source"]

job["source"]

or other metadata to the handler function.
It seems like no matter how I structure the JSON, only

id

id

and

input

input

end up in the job JSON to the handler.

Is this indeed the case?

I prefer not to force additional metadata inside the

input

input

field ... I want a separation between the model's inputs and the handler controllers.

Runpod•16mo ago•

9 replies

Structure of "job" JSON

I understand that at the very least there is

job["id"]

job["id"]

and

job["input"]

job["input"]

and we utilize it.
It will help me a great deal if I could send additional information like

job["source"]

job["source"]

or other metadata to the handler function.
It seems like no matter how I structure the JSON, only

id

id

and

input

input

end up in the job JSON to the handler.

Is this indeed the case?

I prefer not to force additional metadata inside the

input

input

field ... I want a separation between the model's inputs and the handler controllers.

Join the Discord to ask follow-up questions and connect with the community

We're a community of enthusiasts, engineers, and enterprises, all sharing insights on AI, Machine Learning and GPUs!

21,906 Members