Skip to content

.NET Aspire orchestration overview is very long #2677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
JamesNK opened this issue Feb 26, 2025 · 2 comments
Open

.NET Aspire orchestration overview is very long #2677

JamesNK opened this issue Feb 26, 2025 · 2 comments
Assignees
@IEvangelist @alistairmatthews
Labels
📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@JamesNK
Copy link
Member

JamesNK commented Feb 26, 2025 •
edited by sequestor bot
Loading

Describe the issue or suggestion

This page is getting very long. Consider splitting it up.

Associated WorkItem - 417489
@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Feb 26, 2025
@davidfowl
Copy link
Member

+100

@alistairmatthews
Copy link
Contributor

alistairmatthews commented Apr 3, 2025 •
edited
Loading

Hi @JamesNK and @davidfowl, I'm working on this one. I reckon it makes most sense to split it into 3, like this (each top level bullet will be an article):

  • .NET Aspire orchestration overview
    • Current intro paragraphs
    • Define the app model
    • App host project
    • Built-in resource types
    • Reference resources
    • Reference existing resources
    • Execution context
  • Orchestrate resources in .NET Aspire
    • Configure explicit resource start
    • Waiting for resources
      • Forcing resource start in the dashboard
    • APIs for adding and expressing resources
      • Express container resources
      • Customize container resources
    • Container resource lifecycle
    • Container resource lifetime
    • Resource relationships
  • App host life cycles
    • Register a life cycle hook

This third article on life cycles might be better integrated into Eventing in .NET Aspire. What do you think?

@IEvangelist IEvangelist added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed ⌚ Not Triaged Not triaged labels Apr 3, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. label Apr 3, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 4, 2025
@alistairmatthews alistairmatthews mentioned this issue Apr 4, 2025
Closed
@IEvangelist IEvangelist moved this from 🔖 Ready to 👀 In review in dotnet/docs April 2025 sprint project Apr 8, 2025
@adegeo adegeo removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. label Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IEvangelist IEvangelist

@alistairmatthews alistairmatthews

Labels
📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
dotnet/docs April 2025 sprint project
Status: 👀 In review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Split Aspire Orchestration Overview article alistairmatthews/docs-aspire
5 participants
@davidfowl @JamesNK @IEvangelist @alistairmatthews @adegeo