Evaluate an Aspire integration for grate

Aperta
#955 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@erikbra ci sta già lavorando.

Dal 11/11/2026.

  • #957 di @erikbra — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
devops

Direzione di ricerca

Start by reviewing grate's CLI or container usage and Aspire's existing orchestration capabilities; the issue names no specific files or tests. Compare those options with a hosting integration and documentation example, covering database readiness, migration outcomes, secrets, scripts, compatibility, packaging, and maintenance. Document representative use cases, a proposed usage example, and how startup ordering would be verified, then record a recommendation with rationale and bounded follow-up work if proceeding.

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

Descrizione

Is your feature request related to a problem? Please describe.

For developers using grate in an Aspire application, assess whether a dedicated integration could simplify running SQL migrations as part of application orchestration. The use case to evaluate is starting a database, running grate, and allowing dependent applications to start only after migrations complete successfully.

Describe the solution you'd like

Investigate the value, feasibility, and maintenance cost of an Aspire integration for grate, and recommend whether to proceed.

The assessment should cover:

  • The developer experience for declaring a migration resource in an AppHost, referencing a database, and supplying SQL scripts and grate options.
  • How database readiness, successful migration completion, and migration failures should affect dependent application startup.
  • Connection strings and secrets, script paths or mounts, logs, exit codes, and cancellation.
  • Suitable initial database providers, supported Aspire/.NET versions, and the boundary between local development and deployment scenarios.
  • Packaging, distribution, versioning, and ongoing maintenance responsibilities.

Describe alternatives you've considered

Compare a dedicated hosting integration/package with using grate's CLI or container through Aspire's existing orchestration capabilities, and with providing documentation and an example only. Also consider keeping migration execution separate from Aspire, for example in a delivery pipeline.

Additional context

This issue is an investigation; it does not commit the project to implementing or publishing an integration.

Completion criteria:

  • Document representative use cases and the expected benefit over the alternatives.
  • Compare the integration approaches and record constraints, compatibility considerations, and maintenance costs.
  • Describe a proposed usage example and how success/failure ordering would be verified. If a small spike is needed to resolve feasibility questions, record its findings and limits.
  • Record a recommendation to proceed, defer, or decline, with rationale. If proceeding, identify a bounded first implementation and create linked follow-up work.
Lingua principale
C#
Stelle
305
Fork
59
Merge medio
1g 27m
PR unite (30g)
79

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 grate-devs/grate

Tutte le issue di grate-devs/grate

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.