Description
Using CWL-Airflow, it would be possible (technically) to convert a CWL Workflow definition automatically.
This should be investigated to offer the bridge seamlessly for a platform using Airflow, which would provide a way to immediately gain OGC API - Processes interface via CWL deployment.
However, tests must be done for the special EO-data edge-cases and specific structures that OGC API - Processes defines, since they are not all natively CWL-defined. For example, STAC collections I/O or similar might not be directly transferable to CWL-Airlfow, so the conversion might still need to happen at Weaver level before forwarding the CWL-native workflow to Airflow.
References
Description
Using CWL-Airflow, it would be possible (technically) to convert a CWL Workflow definition automatically.
This should be investigated to offer the bridge seamlessly for a platform using Airflow, which would provide a way to immediately gain OGC API - Processes interface via CWL deployment.
However, tests must be done for the special EO-data edge-cases and specific structures that OGC API - Processes defines, since they are not all natively CWL-defined. For example, STAC collections I/O or similar might not be directly transferable to CWL-Airlfow, so the conversion might still need to happen at Weaver level before forwarding the CWL-native workflow to Airflow.
References