Most DAGs use a workflow service endpoint that only exists on Azure's implementation of ingestion-workflow service
These DAGs (recently merged) all use an endpoint that only Azure has:
- csv_ingestion_sas_storage.py
- csv_ingestion_sas_unit_crs_relationships_storage.py
- csv_ingestion_sas_unit_crs_storage.py
- csv_ingestion_sas_unit_storage.py
- csv_parser_http_operator.py
The top 4 listed use this endpoint: https://{dns_host}/api/workflow/v1/workflow/{workflow_id}/workflowRun/{run_id}/getSignedUrl
Looking at ingestion-workflow, this endpoint only exists in Azure's provider code:
Therefore, unless it is merged to core code no other provider can support these DAGs.
Will this endpoint be in core code on ingestion-workflow?
The other dag listed "csv_parser_http_operator" hits an endpoint called 'api/parser/v2/ingestion' which doesn't exist as far as I'm aware.