Expose OpenEO-Identifier header from sync processing response by Copilot · Pull Request #893 · Open-EO/openeo-python-client

Copilot · 2026-04-28T06:11:13Z

OpenEO API v1.3 added an OpenEO-Identifier response header to POST /result to expose a tracking identifier for synchronous processing requests. This PR wires that header through to callers.

Changes

Connection.download() / Connection.execute(): Automatically log the OpenEO-Identifier at DEBUG level when present — no extra code required to see it in logs
Tests added for the new auto-logging behaviour; CHANGELOG updated

Usage

# Enable DEBUG logging — identifier is logged automatically with no extra code
import logging
logging.basicConfig(level=logging.DEBUG)

connection.download(...)   # logs "Synchronous processing request identifier: r-001"
connection.execute(...)    # same

…og OpenEO-Identifier Agent-Logs-Url: https://github.com/Open-EO/openeo-python-client/sessions/72ac5e9e-be54-4fc5-acef-10648287ee35 Co-authored-by: soxofaan <44946+soxofaan@users.noreply.github.com>

soxofaan · 2026-04-28T09:33:08Z

+        validate: Optional[bool] = None,
+        auto_decode: bool = True,
+        on_response_headers: Optional[Callable[[Mapping], None]] = None,
+    ) -> Union[dict, requests.Response]:


I don't think that is necessary in this PR

Reverted in fb8646f.

soxofaan · 2026-04-28T09:33:39Z


-    def execute(self, *, validate: Optional[bool] = None) -> dict:
+    def execute(self, *, validate: Optional[bool] = None, on_response_headers: Optional[Callable[[Mapping], None]] = None) -> dict:
        """Executes the process graph."""


I don't think this is necessary in this PR

Reverted in fb8646f.

soxofaan · 2026-04-28T09:34:05Z

+    """Test that on_response_headers callback is called with response headers from execute."""
+    dummy_backend.next_result = {"result": 42}
+    results = []
+    s2cube.execute(on_response_headers=results.append)


This does not test the added feature

Removed in fb8646f.

soxofaan · 2026-04-28T09:34:19Z

+    """Test that on_response_headers callback is called with response headers from VectorCube.execute."""
+    results = []
+    vector_cube.execute(on_response_headers=results.append)
+    assert results == [{"OpenEO-Identifier": "r-001"}]


this is not a test for the added feature

Removed in fb8646f.

soxofaan · 2026-04-28T09:34:52Z

+        {"foo1": {"process_id": "foo"}},
+        on_response_headers=results.append,
+    )
+    assert results == [{"OpenEO-Identifier": "r-001"}]


this is not a test for the added feature

Removed in fb8646f.

soxofaan · 2026-04-28T09:35:04Z

+    dummy_backend.next_result = {"result": 42}
+    connection = openeo.connect(dummy_backend.connection.root_url, on_response_headers_sync=results.append)
+    connection.execute({"foo1": {"process_id": "foo"}})
+    assert results == [{"OpenEO-Identifier": "r-001"}]


this is not a test for the added feature

Removed in fb8646f.

soxofaan · 2026-04-28T09:35:26Z

+
+
+def test_download_openeo_identifier_logging(dummy_backend, tmp_path, caplog):
+    import logging


avoid this local import

Fixed in fb8646f — logging is already imported at the top of the file, so the local import was removed.

soxofaan · 2026-04-28T09:35:33Z

+
+
+def test_execute_openeo_identifier_logging(dummy_backend, caplog):
+    import logging


avoid this local import

Fixed in fb8646f.

…ve related tests, fix local imports Agent-Logs-Url: https://github.com/Open-EO/openeo-python-client/sessions/a5d2dc5a-87ff-4776-8246-7f2a8e337784 Co-authored-by: soxofaan <44946+soxofaan@users.noreply.github.com>

Copilot · 2026-04-28T09:41:42Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

oeo.test
- Triggering command: /usr/bin/python python -m pytest tests/rest/ -x -q (dns block)
provider.test
- Triggering command: /usr/bin/python python -m pytest tests/rest/ -x -q (dns block)
stac.test
- Triggering command: /usr/bin/python python -m pytest tests/rest/ -x -q (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

soxofaan · 2026-04-29T07:31:42Z

overruled by 14cc3d7

Initial plan

021772c

Copilot AI assigned Copilot and soxofaan Apr 28, 2026

Copilot started work on behalf of soxofaan April 28, 2026 06:11 View session

Copilot AI linked an issue Apr 28, 2026 that may be closed by this pull request

expose OpenEO-Identifier header from sync response #890

Closed

Add on_response_headers to DataCube.execute and VectorCube.execute, l…

ee402ae

…og OpenEO-Identifier Agent-Logs-Url: https://github.com/Open-EO/openeo-python-client/sessions/72ac5e9e-be54-4fc5-acef-10648287ee35 Co-authored-by: soxofaan <44946+soxofaan@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add OpenEO-Identifier header from sync response~~ Expose OpenEO-Identifier header from sync processing response Apr 28, 2026

Copilot finished work on behalf of soxofaan April 28, 2026 06:21

Copilot AI requested a review from soxofaan April 28, 2026 06:21

soxofaan requested changes Apr 28, 2026

View reviewed changes

Copilot started work on behalf of soxofaan April 28, 2026 09:36 View session

Copilot finished work on behalf of soxofaan April 28, 2026 09:41

Copilot AI requested a review from soxofaan April 28, 2026 09:41

soxofaan closed this Apr 29, 2026

soxofaan deleted the copilot/expose-openeo-identifier-header branch April 29, 2026 07:37



		def test_download_openeo_identifier_logging(dummy_backend, tmp_path, caplog):
		import logging



		def test_execute_openeo_identifier_logging(dummy_backend, caplog):
		import logging

Conversation

Copilot AI commented Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Usage

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Apr 28, 2026

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

soxofaan commented Apr 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Apr 28, 2026 •

edited

Loading