Map WebJobs Extension RPC data sources onto the gRPC host endpoints #9292
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.
This PR is to a feature branch. The intention is to review, check in, build & release feature branch to internal feed. After testing and validation by partners, we will then merge feature branch into
dev
.This PR consumes the new
Microsoft.Azure.WebJobs.Rpc.Core
package (from our ADO feed for now), which brings in a single contractWebJobsRpcEndpointDataSource
. This type is used by WebJobs extensions via theMicrosoft.Azure.WebJobs.Extensions.Rpc
package to register and export their RPC extensions (only gRPC supported at this time). We then discover all of those data sources from the active script host and map them into the existing AspNetCore server we use for our own gRPC communication between host and worker. The end result here is that WebJobs extensions can easily hand off their gRPC service implementations to us for endpoint mapping. This enables custom RPC scenarios between worker and host.Issue describing the changes in this PR
resolves #9291
Pull request checklist
release_notes.md