[App Service] Document runtime container identity and completion correlation for webapp exec

Aperta
  • Qualcosa non va?
#34,314 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
cloud, python
Ambito
cloud, documentation

Direzione di ricerca

Start with src/azure-cli/azure/cli/command_modules/appservice/webapp_exec.py, which handles the shell (/exec/shell) and detached (/exec/execute, HTTP 202) paths, and with the App Service 2026-07-15 openapi.json ContainerInfo and restart definitions. The work is to find or confirm the supported server-side documentation that joins instance, container, image digest and execution identities, and to report where that interface is not customer-facing. Done means a sourced answer, or a maintainer-confirmed boundary, not a code change.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

customer-reported

Which supported, versioned customer API or protocol can correlate a Linux App Service main-app command with its actual running container and a particular configuration/restart operation?

I am looking for documented response fields and semantics for these relationships:

  1. The actual selected app instance and container occurrence, including how its identity changes on replacement or restart.
  2. That occurrence's actual immutable running-image digest, with the digest type defined (for example, image manifest versus image configuration), rather than only the requested image reference.
  3. A command/execution identity tied to that occurrence, its returned stream, and completed stdout/stderr and exit status, including interruption and reconnect/replay behavior.
  4. The specific configuration or restart operation tied to the resulting container occurrence, so an older still-running container or an unrelated platform recycle cannot be mistaken for that operation's result.

The public sources I checked establish parts of the interface:

I have not found the documented joins between these observations. Could you point to the supported server protocol or runtime-observation API, its applicable versions, and the exact returned fields/correlation rules? In particular, are instance/container identifiers shared between the ARM observations and the SCM exec channel, and what guarantees apply while a container is being replaced?

If any relationship is outside the supported customer interface, a clarification of that boundary would help. If the server protocol belongs to another App Service team or tracker, please point to the appropriate documentation or destination.

Lingua principale
Python
Stelle
4.7k
Fork
3.5k
Merge medio
4g 21h
PR unite (30g)
50

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/azure-cli

Tutte le issue di Azure/azure-cli

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.