-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement a gRPC event trigger to publish events to NATS (#377)
* Create event-trigger grpc server * Dockerise event-trigger * Helm + kustomize setup * Replace http webhook client with grpc * Add to upstream service unit tests * Rework publishing to be via a PublishHandler interface * Update helm configuration and docker images * Add nats event server/nats event bus functional test. * Change service name to run-completion-event-trigger * Update sensor datakey for use with new run completion format * Remove unused event source webhook * Remove grpc config for deployment in kustomize * Move helm chart for triggers into statusFeedback eventing loop * Remove triggers from kustomization config * Update Protobuf to use Enum and client + server implementations * Apply suggestions from pr * Drop nats from grpc client name in controller webhook * Retain data key within body of run-completion when sent to NATS * Trigger namespace configurable in helm deployment * Update trigger to use zapr for logging * Update webhook to support run completion events with no provided RunName --------- Co-authored-by: Ankitha-Krisshnan <[email protected]> Co-authored-by: chr12c <[email protected]>
- Loading branch information
1 parent
8918170
commit 5e41f9d
Showing
39 changed files
with
3,042 additions
and
355 deletions.
There are no files selected for viewing
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
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.