-
Notifications
You must be signed in to change notification settings - Fork 647
Add WaitBehavior to WaitForResourceHealthyAsync #7650
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
@davidfowl @eerhardt this fixes #7601 however I am wondering if there is an API design issue here. We are adding an overload to I'm wondering whether we need either a new enumeration here or a new enumeration value. A new enumeration value would be a bit strange because then we would have enumeration values that only apply in certain contexts which is why I lead to a new enumeration - but Arguably we could rename |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs
Outdated
Show resolved
Hide resolved
…e.cs Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Merging this now we can come back with the enum rename since its a breaking change (this would just be one more place where it breaks but this is a less frequent usage scenario I think). |
/backport to release/9.1 |
Started backporting to release/9.1: https://github.com/dotnet/aspire/actions/runs/13401316958 |
@mitchdenny can you look at my branch and apply the delta?? I think this PR is incomplete |
Ok |
Edit: I see this got renamed in #7668 |
Description
Added an overload to the
WaitForResourceHealthyAsync
method that allows us to specify the wait behavior if the resource fails to start. When set toStopOnDependencyFailure
if the resource enters a failed to start state it will throw an exception.Fixes #7601
Checklist
<remarks />
and<code />
elements on your triple slash comments?breaking-change
template):doc-idea
template):