Improvements for execution context
Today, the execution context requires:
{
"Payload": {
"AppKey": "",
"data-partition-id": "partition"
},
"id_token": "",
"persistent_id": "filename.vds",
"vds_url": "sd://partition/sub-project",
"work_product_id": "",
"file_record_id": ""
}
This could be simplified to only require work_product_id and file_record_id as all the information needed is present in those records.
Suggested new execution context:
{
"data-partition-id": "partition",
"work_product_id": "",
"file_record_id": ""
}
The persistent_id would be generated similar to what the SEG-Y to ZGY DAG does: Output file path will be generated from the input: insert a GUID after the file name, replace .sgy extension with .vds.
Note, this removes the need for id_token
Edited by Sacha Brants