Include job_options in GET /jobs/{job_id} response#486
Draft
Include job_options in GET /jobs/{job_id} response#486
Conversation
…ponse Agent-Logs-Url: https://github.com/Open-EO/openeo-python-driver/sessions/e0c24630-bd0e-4ccd-9bad-eeeb2ba81beb Co-authored-by: jdries <5937096+jdries@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add job options to GET /jobs/{job_id} response
Include job_options in GET /jobs/{job_id} response
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Job options submitted via
POST /jobswere stored but never surfaced back to the user onGET /jobs/{job_id}.Changes
BatchJobMetadata.to_api_dict()— whenfull=True, spreadsjob_optionsdict entries as top-level properties in the response, per the openEO API convention for custom backend propertiestests/test_views.py— addstest_get_job_info_with_job_optionscovering the end-to-end round-tripExample
A job created with:
{ "process": {...}, "driver-memory": "3g", "executor-memory": "5g" }Now returns those options in
GET /jobs/{job_id}:{ "id": "job-123", "status": "created", "process": {...}, "driver-memory": "3g", "executor-memory": "5g" }