Propagate FunctionInvocationId for single-instance and bulk purge requests

Abierto
  • ¿Algo no está bien?
#630 0 comentarios 0 reacciones 0 asignados Ver en GitHub

@Fire162 ya está trabajando en esto.

Desde el 3/11/2026.

  • #631 de @Fire162 — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
api

Línea de trabajo

Start in azure/durable_functions/models/DurableOrchestrationClient.py at purge_instance_history and purge_instance_history_by, then read azure/durable_functions/models/utils/http_utils.py to understand the existing DELETE helper and header contract. Add regression coverage for both purge calls, including clients with distinct invocation IDs and without one; done means the outgoing header is correct and other purge behavior remains unchanged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Needs: Triage :mag:

Summary

Python Durable client purge operations do not forward the originating Azure Functions invocation ID, so the host cannot emit the correlated ClientOperationReceived logs needed by the remaining Python purge E2E assertions in Azure/azure-functions-durable-extension#3327.

This is a source-inspection report, not a deployed-application incident. The scope is the existing single-instance and bulk purge APIs, not adding new orchestration capabilities.

SDK line and next-generation tracking

This issue covers the stable Python v1 HTTP implementation in this repository; the current stable PyPI release is azure-functions-durable 1.7.0. The newer Python v2 Functions SDK is maintained in microsoft/durabletask-python under azure-functions-durable and has a published 2.0.0rc3 preview. Its separate gRPC invocation-metadata gap is tracked in microsoft/durabletask-python#314.

The extension's BasicPython app currently has an unversioned azure-functions-durable requirement, which normally selects the stable release rather than opting into v2 previews. Keep the two transport/version scopes distinct; maintainers can resolve the stable-line dependency through a backport or an explicit migration to a fixed newer SDK, rather than treating this issue as the only current Python implementation.

Current behavior and source evidence

Verified on dev at badf8016eb8186958ebd07908576deb1bb33e945:

Reproduction and expected behavior

Construct a DurableOrchestrationClient with a known, valid invocation ID, capture or mock its outgoing HTTP requests, and invoke each purge API with valid arguments. The current call sites omit the ID even though the DELETE helper supports it. Both outgoing requests should carry X-Azure-Functions-InvocationId equal to the originating invocation ID; purge URLs, filters, response parsing, and error behavior should remain unchanged.

Acceptance Criteria

  • Both purge APIs pass the client's invocation ID to the existing DELETE helper.
  • Regression tests cover single-instance and filtered bulk purge and verify the actual outgoing header or the helper argument plus the existing transport-header contract.
  • Tests cover distinct invocation IDs and clients without an invocation ID; no ID is fabricated or leaked between clients.
  • Existing purge behavior remains unchanged apart from the correlation header.
  • Record the published SDK version containing the fix in this issue so the extension E2E dependency can be updated and its Python PurgeInstances exemption removed.

Related

This issue tracks the upstream SDK dependency only. Enabling mandatory extension E2E assertions follows after the fixed package is available.

Lenguaje dominante
Python
Estrellas
157
Forks
71
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/azure-functions-durable-python

Todos los issues de Azure/azure-functions-durable-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.