-
Notifications
You must be signed in to change notification settings - Fork 2
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
Implement the WPS-T methods execute() and status() #61
Comments
this supercedes #47 ? |
Implemented by Drew and merged into develop, tested by both Luca and Mike. |
Future work will need to be done to perform validation of the inputs and outputs based on the schema of the registered process. This should occur in the function behind the execute endpoint. Following validation, the inputs will need to be passed to the DAG run. Currently no inputs are passed through from the endpoint to the DAG run trigger. This is a major limitation of our current implementation of the execute() method. |
Description: Using the stubbed OGC API, implement the execute() method to submit a job to SPS Airflow, and the status() method to retrieve its status.
Acceptance Criteria:
o Demonstrated invocation of the execute() and status() method via any HTTP client (for example, CURL)
o Nightly test to execute and monitor a simple CWL workflow via the WPS-T API
The text was updated successfully, but these errors were encountered: