Establish authoritative SessionGroup membership and session catalog lifecycle

Abierto
#2,903 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start by reviewing the linked contracts in #2761, #2760, #2665, #2669, #2670, #2671 and #2672, then trace the existing Go session and history creation, publication, lookup and activation paths. Define the catalog authority, persistence and failure model before implementing; the issue requires review before implementation and deterministic tests at the storage and activation boundaries. Done means membership, publication and tombstones remain authoritative across interruptions, deletion, restart and owner changes, with delegation behavior qualified against #2671.

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

Descripción

Outcome

An authoritative catalog records SessionGroup identity, permanent Session/history membership, session existence/publication, and logical deletion independently of whether history bytes already exist. Deletion and retained references cannot re-enable execution/access or permit identity reuse.

Parent: #2666, under #2659. This carries catalog and lifecycle obligations moved out of #2761's bounded group-lease contract and two-history memory proof. #2761 supplies ownership/fencing primitives, not catalog authority.

Scope

  • Define and implement authoritative group/session creation, member registration, publication, lookup and logical deletion. A group may be empty and has no intrinsically distinguished root member.
  • Assign each Session/history permanently to one group. Register new members under the correct group authority; do not implement cross-group migration. Distinguish membership from initialized history, loaded runtimes, principal authorization and execution authority.
  • Review the catalog/manifest persistence and creation/publication ordering contract, including interruptions before any accepted history exists. A backend index or routing table is not a competing catalog.
  • Specify deletion tombstones/identity retirement, activation/access checks and cleanup without claiming immediate physical purge. Session and group identities are not reused or silently reassigned.
  • Coordinate delegation lifecycle policy with #2671: where a parent/root deletion must disable owned delegated work, enforce that policy consistently without assuming every group member is a child or that deleting any member deletes its peers. Retained history/environment references cannot resurrect disabled or expired resources.

Acceptance

  • Catalog and membership authority, storage schema, failure model, access/execution boundaries and Go/stored/wire compatibility are reviewed before implementation.
  • Creation/member publication interrupted before, during and after first-history acceptance produces explicit reconcilable states, without duplicate identity or an independently activatable orphan.
  • Concurrent registration/activation and stale-owner operations cannot assign a member to two groups, bypass the group lease or reinterpret absent history as absent membership.
  • Logical deletion prevents prohibited activation/access and ID reuse even before history creation, after runtime eviction, and after restart or owner change; cleanup is distinct from deletion authority.
  • Delegation deletion/cancellation integration is qualified with #2671, including stale child advancement and direct API Team creation where applicable. SessionGroup itself has no required root.
  • Deterministic tests exercise actual catalog/storage and activation boundaries with isolated state, plus bounded handling of corruption/uncertainty. Residual deployment qualification is explicitly assigned.

Dependencies and boundaries

Coordinate #2761 leases/fencing, #2760 durable history, #2665 interrupted recovery, #2669 shared controls, #2670 authorization/provenance, #2671 delegation and #2672 final cutover qualification. Reuse accepted history identities without importing the legacy Session aggregate or treating diagnostic InstanceID as authority.

No automatic cross-owner private-output replay, cross-group migration, implicit cross-history transaction, production cutover, physical purge promise or schema/API break is authorized by filing this issue. Preserve the existing separation between principal access and execution leasing.

Lenguaje dominante
Go
Estrellas
309
Forks
29
Merge medio
15 h 56 min
PR fusionados (30 d)
225

Preparar el entorno

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 stacklok/mecatl

Todos los issues de stacklok/mecatl

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.