Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Plan layer: run provider plan servers, add provider planning to simulate

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

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, go, kubernetes
Área
cli, cloud, infrastructure

Línea de trabajo

Empieza leyendo design/one-pager-cli-simulate.md y el diseño aceptado de crossplane/cli#181; después revisa project simulate y resource simulate de los issues #367 y #368. Confirma el diseño aprobado de upjet PlanService en upjet#694 antes de implementar la orquestación y el enrutamiento internos de plan-server. Se considera terminado cuando ambos comandos produzcan planes del provider o diffs marcados como fallback, admitan los flags documentados y cumplan los criterios indicados de salida y de vista previa de la actualización.

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

Descripción

enhancement
What

Implement the provider layer from the accepted design (crossplane/cli#181,design/one-pager-cli-simulate.md): run provider packages as local plan servers and route rendered/input MRs to them, upgrading both simulate commands from client-side diffs to provider-computed plans.

Blocked on the crossplane/upjet PlanService design PR. this issue follows whatever that review approves. https://github.com/crossplane/upjet/pull/694

Scope:

  • Image sources. Project dependsOn for project simulate; providers installed on the current cluster context for resource simulate; --provider-images overrides either. The override only changes the image list, never routing.
  • Container orchestration. Start each provider image with its internal plan-server entrypoint as a local Docker container, following render's runtime conventions (pull policy, cleanup on exit). Deterministic container names derived from the image digest. --keep-plan-servers leaves containers running for later runs to reuse; a changed image never matches a stale server.
  • Routing. Call each server's GetInfo, build the routing table from declared API groups. A resource with no route is detected up front.
  • Matching. Match rendered to live composed resources by the crossplane.io/composition-resource-name annotation, falling back to group/kind/name; merge the live MR's external-name annotation and status into the request. Live resources with no rendered counterpart enter the plan as deletes.
  • Rendering responses. Field changes inline in CRD terms, sensitive values redacted, computed values as (known after apply), replacement warnings inline, provider diagnostics under their resource. Replaces counted separately in the summary (N requires replacement) with the wedge warning from the design.
  • Fallback. A resource with no plan server gets the client-side diff, marked [?], with the closing approximate warning. --skip-plan skips the plan layer entirely (no containers start).
  • Provider upgrade preview. resource simulate --all --provider-images <image>: enumerate managed resources of the served groups from the cluster, plan each with its own spec as desired and itself as live; anything that is not a no-op is a finding.
Acceptance criteria
  • Both simulate commands produce provider-computed plans for resources whose provider serves the plan protocol, and [?] client-side diffs for the rest, in one run.
  • Routing comes only from GetInfo; no image-name parsing, no registry queries.
  • --provider-images, --skip-plan, --keep-plan-servers behave as documented; leftover containers follow the naming scheme and are reused only on digest match.
  • --all previews a provider upgrade with zero cloud API calls and no cloud credentials.
  • Replaces are counted separately and never presented as destroy-and-recreate; the unsynced-until-replaced warning prints.
  • JSON/YAML output includes actions, field changes, replace information, and diagnostics, sufficient for a PR bot to gate on "any replace anywhere".
Out of scope
Dependencies

Depends on the project simulate https://github.com/crossplane/cli/issues/367 and resource simulate https://github.com/crossplane/cli/issues/368 issues, and on the approved upjet PlanService design.

Lenguaje dominante
Go
Estrellas
19
Forks
33
Merge medio
3 d 4 h
PR fusionados (30 d)
40

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 crossplane/cli

Todos los issues de crossplane/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.