Skip to content

Conform more closely to OGC Processes API spec #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 19, 2024

Conversation

drewm-swe
Copy link
Contributor

@drewm-swe drewm-swe commented Sep 9, 2024

Purpose

  • This PR revamps the OGC API Processes API implementation to conform more closely to the specification of 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

  • SPS was successfully deployed with this version of the OGC API server. Following deployment, the 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. The cwl_dag was also successfully undeployed. This process was also performed using the unity-sds-client integration of this client.

@drewm-swe drewm-swe changed the title 129 arbitrary parameters Conform more closely to OGC Processes API spec Sep 19, 2024
@drewm-swe drewm-swe marked this pull request as ready for review September 19, 2024 02:58
@drewm-swe drewm-swe merged commit 36419df into develop Sep 19, 2024
12 checks passed
@drewm-swe drewm-swe deleted the 129-arbitrary-parameters branch September 19, 2024 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants