Skip to content

Handling of UDP process graph id #394

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

Closed
soxofaan opened this issue May 17, 2021 · 2 comments
Closed

Handling of UDP process graph id #394

soxofaan opened this issue May 17, 2021 · 2 comments
Labels
bug minor requires a minor-version (x.1.0 for example)
Milestone

Comments

@soxofaan
Copy link
Member

conflict:

openeo-api/openapi.yaml

Lines 2265 to 2268 in f303d65

To simplify exchanging user-defined processes, the property `id` can be part of
the request body. If the values don't match, the value for `id` gets
replaced with the value from the `process_graph_id` parameter in the
path.

openeo-api/errors.json

Lines 205 to 211 in f303d65

"ProcessGraphIdDoesntMatch": {
"description": "If a user-defined process is stored and the ID in the request path and the JSON document are not equal.",
"message": "The ids in the path and in the document don't match.",
"http": 400,
"tags": [
"User-Defined Processes"
]

@m-mohr
Copy link
Member

m-mohr commented May 17, 2021

Indeed. What's the better behavior? But the openapi.yaml is normative, errors.json is not, so the next step would probably to remove the ProcessGraphIdDoesntMatch error. It's probably also not mentioned anywhere?!

@m-mohr m-mohr added this to the 1.2.0 milestone May 17, 2021
@m-mohr
Copy link
Member

m-mohr commented May 18, 2021

Removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug minor requires a minor-version (x.1.0 for example)
Projects
None yet
Development

No branches or pull requests

2 participants