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

jobs should be a top-level resource #838

Closed
MartinPontius opened this issue Jan 3, 2022 · 2 comments
Closed

jobs should be a top-level resource #838

MartinPontius opened this issue Jan 3, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@MartinPontius
Copy link
Contributor

Description
Currently Jobs is a sub-resource of Processes. However, according to the specification it should be a top-level resource, see e.g.
https://docs.ogc.org/is/18-062r2/18-062r2.html#toc0 or opengeospatial/ogcapi-processes#69

Steps to Reproduce
Visit, e.g., the demo server: https://demo.pygeoapi.io/master/processes/hello-world/jobs

Expected behavior
Jobs is a top-level resource, e.g. https://demo.pygeoapi.io/master/jobs

Screenshots/Tracebacks

Environment

Additional context

@MartinPontius MartinPontius added the bug Something isn't working label Jan 3, 2022
tomkralidis added a commit to tomkralidis/pygeoapi that referenced this issue Jan 4, 2022
tomkralidis added a commit that referenced this issue Jan 4, 2022
* update OAProc jobs as a top-level resource (#838)

* update config

* update copyright year
@tomkralidis
Copy link
Member

@MartinPontius thanks for the report. This is now merged in master. Can you verify?

@MartinPontius
Copy link
Contributor Author

@tomkralidis Thank you for the quick fix! I did some tests and everything seems to work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants