-
Notifications
You must be signed in to change notification settings - Fork 462
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
.NET Aspire Eventing API #5223
Merged
Merged
.NET Aspire Eventing API #5223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-issue-labeler
bot
added
the
area-integrations
Issues pertaining to Aspire Integrations packages
label
Aug 8, 2024
mitchdenny
added
area-app-model
Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
and removed
area-integrations
Issues pertaining to Aspire Integrations packages
labels
Aug 8, 2024
eerhardt
reviewed
Aug 8, 2024
eerhardt
reviewed
Aug 8, 2024
eerhardt
reviewed
Aug 8, 2024
karolz-ms
reviewed
Aug 8, 2024
davidfowl
reviewed
Aug 8, 2024
davidfowl
reviewed
Aug 8, 2024
mitchdenny
changed the title
DRAFT: Pub sub spike with database initialization
.NET Aspire Eventing API
Aug 12, 2024
mitchdenny
force-pushed
the
mitchdenny/pubsub-eventing
branch
from
August 12, 2024 04:53
2a4da52
to
ee2d070
Compare
This was referenced Aug 12, 2024
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
mitchdenny
force-pushed
the
mitchdenny/pubsub-eventing
branch
2 times, most recently
from
August 12, 2024 22:52
f7dd3d3
to
7cc4263
Compare
@radical this (build failures) looks like it is related to building and testing the playground projects? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Blocked on: #5273 |
eerhardt
reviewed
Aug 14, 2024
eerhardt
reviewed
Aug 14, 2024
…stgres stuff ahead of a merge.
mitchdenny
force-pushed
the
mitchdenny/pubsub-eventing
branch
from
August 15, 2024 00:41
07470ec
to
c3f3f1c
Compare
davidfowl
approved these changes
Aug 15, 2024
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR explores the idea of introducing an eventing mechanism into .NET Aspire. It adds an
Eventing
property to the builder and injects anIDistributedApplicationEventing
service into DI which can be used throughout the lifecycle of the application to fire off events.Any code that can access the application builder or resolve the service from DI can publish an event and an event is extensible. Events are global so it is up to the subscriber to define the callback to filter out specific events they are not interested in (although event of a specific type only go to subscribers for that type in the current implementation).
Related #5234 (API Design issue)
Checklist
<remarks />
and<code />
elements on your triple slash comments?Microsoft Reviewers: Open in CodeFlow