Conform more closely to OGC Processes API spec #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
OGC API Processes - Part 2: Deploy, Replace, Undeploy
. Future work remains to for the implementation to fully conform to the spec. In its current form, the implementation now provides the ability to request execution of an OGC Process with arbitrary parameters that get pass through to the EMS/ADES (Airflow).Proposed Changes
Issues
Testing
cwl_dag
process was deployed using the OGC API and executed multiple times with different inputs. The different inputs were reflected in the DAG run that was triggered by the execution. Job status was polled using the job status endpoint. Executions/jobs were also dismissed and dismissed jobs were verified to have been deleted from the list of OGC jobs as well as from the list of DAG runs. Thecwl_dag
was also successfully undeployed. This process was also performed using theunity-sds-client
integration of this client.