You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The files are largely identical, with only minor differences such as:
usage of quotes for values
usage of array format vs yaml list format for lists
name of the package: water-bodies (water-bodies.cwl) vs. water_bodies (app-water-bodies-cloud-native.1.5.0.cwl)
However, the name difference in the Swagger UI actually causes an process deployment error in the Swagger UI with the default W parameter because it expects the name water-bodies.
Also, if you go to 'deploy a new process' endpoint (POST /processes) and click 'Try it out', then change the Request Body parameter from application/cwl+yaml to application/ocaapppkg+json, the data changes from a valid CWL to something that looks like a JSON schema:
However, I have updated the water-bodies.cwl to now use Terradue's latest example. 3394f3b
Packaged within that commit is a fair amount of refactoring too.
@rconway , I have refactored a lot of the IAM BB and have references sections of that within this Processing BB to try to avoid duplication. It's probably worth you having a look through the commit that I have just referenced
The CWL process definition is different in the Deployment Guide and in the Swagger UI:
https://raw.githubusercontent.com/EOEPCA/deployment-guide/2.0-beta/scripts/processing/oapip/examples/water-bodies.cwl
https://github.com/Terradue/ogc-eo-application-package-hands-on/releases/download/1.5.0/app-water-bodies-cloud-native.1.5.0.cwl
The files are largely identical, with only minor differences such as:
water-bodies.cwl
) vs. water_bodies (app-water-bodies-cloud-native.1.5.0.cwl
)However, the name difference in the Swagger UI actually causes an process deployment error in the Swagger UI with the default W parameter because it expects the name water-bodies.
Also, if you go to 'deploy a new process' endpoint (
POST /processes
) and click 'Try it out', then change the Request Body parameter fromapplication/cwl+yaml
toapplication/ocaapppkg+json
, the data changes from a valid CWL to something that looks like a JSON schema:which, of course, also fails to deploy correctly.
The text was updated successfully, but these errors were encountered: