Add support for multi deployment using workflow cwl

[Nazim-crim]

• fixes Support Multipart CWL Deployment #717

• fixes Support multi-CWL file deployment #874

• relates to CWL guidance improvements + Multipart Deploy/Replace opengeospatial/ogcapi-processes#588

• Add support for multipart Process deployment using multipart/related or multipart/mixed content types,
  allowing simultaneous upload of multiple CWL files (e.g.: class: Workflow and class: CommandLineTool)
  along with optional Process description metadata

  • relates to Support embedded step definition in CWL #56
  • resolves Support Multipart CWL Deployment #717
  • resolves Support multi-CWL file deployment #874

• Add support for CWL $graph representation with multiple entries, enabling deployment of workflows with
  embedded step definitions without manual preprocessing
  (resolves Support embedded step definition in CWL #56).

• Add validation during multipart deployment to ensure at least one class: Workflow is present and properly
  identified as the main workflow from media-type hints or Content-ID references.

• Add CLI support for deploying multiple CWL files by repeating --cwl arguments to automatically generate
  multipart/related request payloads, simplifying deployment of workflows with multiple step definitions.
  The CLI accepts a mixture of local CWL file paths (as JSON or YAML) and remote URL references.
  The server handles Content-Type media-type detection and Content-Location header processing for external
  CWL files to fetch during deployment.

[codecov]

Codecov Report

❌ Patch coverage is 97.68340% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.38%. Comparing base (ea311a3) to head (31dcbdd).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
weaver/processes/utils.py	97.37%	0 Missing and 6 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #968      +/-   ##
==========================================
+ Coverage   88.23%   88.38%   +0.15%     
==========================================
  Files          88       88              
  Lines       20573    20808     +235     
  Branches     2702     2753      +51     
==========================================
+ Hits        18152    18391     +239     
+ Misses       1733     1729       -4     
  Partials      688      688              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

[fmigneault]

Looks good for the features. We just need to document the things that were implemented.

[fmigneault]

In order to properly reflect the added functionalities, the corresponding /rec, /per, /req and /conf elements defined in https://github.com/opengeospatial/ogcapi-processes/pull/588/changes#diff-6dbd783db0ade3c408ddc75d4271f2af2478056344e081a02f48a495fdde4716 need to be added to the weaver/wps_restapi/api.py conformance list.

The should use the ogcapi_proc_part2 prefix. To be placed where other similar definitions about ../cwl/.. can be found, in the corresponding order to make it easier to find/double-check them.

[Nazim-crim]

I only see the /rec , is there something else to add ?

 f"{ogcapi_proc_part2}/rec/deploy-replace-undeploy/deploy-body-cwl-multipart",
f"{ogcapi_proc_part2}/rec/deploy-replace-undeploy/replace-body-cwl-multipart
```",

[fmigneault]

This was tweaked this morning:
https://github.com/opengeospatial/ogcapi-processes/pull/591/changes#diff-0585b5be32577d57efb86c7bea15b3978b38d06c973de723a225f1abac32d977

[Nazim-crim]

I'm having issue understanding the changes / what needs to be taken from this pr

I see this new one

/per/cwl/multipart-cwl-body

and that deploy-body-cwl-multipart has been remove

[fmigneault]

Yes. The 2 previous definitions have been combined into a single one (note the /rec -> /per change).

[Nazim-crim]

So its only this to be added ?
/per/cwl/multipart-cwl-body

Since the other are regarding the w parameter

[fmigneault]

Can we have a few extra tests for error prone cases:

1. With #main set on a CommandLineTool where more than one CommandLineTool is provided and no Workflow is present.
2. With #main set on a CommandLineTool while Workflow has something else.
3. With #main set on both CommandLineTool and Workflow.

In each case, those combination should create a similar error.

[Nazim-crim]

When its a workflow there should always be a #main id ?, only in the case when using with graph right *

[fmigneault]

If there is only 1 workflow, it is safe to assume it is the main if no #main is provided. It should be provided if there is more than one, and it must not be on a non workflow item. Should apply to any dict/graph/multipart variant when dealing with the list of resolved CWLs.

[Nazim-crim]

We dont allow more than 1 workflow in this case

[fmigneault]

We still need to check if there are more than one occurences of #main, such as for case (3) since the workflow > 1: raise condition will not be triggered.