Skip to content
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

Closed
Tracked by #19
LucaCinquini opened this issue Apr 10, 2024 · 3 comments
Closed
Tracked by #19

Implement the WPS-T methods execute() and status() #61

LucaCinquini opened this issue Apr 10, 2024 · 3 comments
Assignees
Labels
dependency Ticket designating a dependency U-SPS

Comments

@LucaCinquini
Copy link
Collaborator

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

@rtapella
Copy link

this supercedes #47 ?

@LucaCinquini
Copy link
Collaborator Author

Implemented by Drew and merged into develop, tested by both Luca and Mike.

@drewm-swe
Copy link
Contributor

drewm-swe commented Jun 13, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Ticket designating a dependency U-SPS
Projects
Status: Done
Development

No branches or pull requests

3 participants