For GCP OSDU environments the name of the DAG that performs the conversion from SEGY to OpenVDS are not consistent.
In the Platform Validation (GCP Dev2) environment the name of the DAG is "Segy_to_vds_conversion_sdms" and in the pre-ship environment name of DAG is "openvds_import" Also, the document that describes how to trigger the workflow needs updating. At present it says to trigger
curl --location --request POST 'https://<base_url>/api/workflow/v1/workflow/openvds_import/workflowRun' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: opendes' \
--header 'Authorization: <Bearer Token>' \
--data-raw '{
"executionContext": {
"url_connection":"Region=us-east-1;AccessKeyId=XXX;SecretKey=XXX;SessionToken=XXX",
"input_connection":"Region=us-east-1;AccessKeyId=XXX;SecretKey=XXX;SessionToken=XXX",
"segy_file":"s3://aws-osdu-sample-data/sample-data/seismic/st0202/stacks/ST0202R08_PS_PSDM_RAW_PP_TIME.MIG_RAW.POST_STACK.3D.JS-017534.segy",
"url":"s3://aws-osdu-sample-data/"
}
}
But know if we one is going to create a File record as well as bingrid, seimictrace and work-product-component records then
url_connection and input_connection do not make sense?