event-bus/

README

  ______               _     ____            
 |  ____|             | |   |  _ \           
 | |____   _____ _ __ | |_  | |_) |_   _ ___
 |  __\ \ / / _ \ '_ \| __| |  _ <| | | / __|
 | |___\ V /  __/ | | | |_  | |_) | |_| \__ \
 |______\_/ \___|_| |_|\__| |____/ \__,_|___/

Overview

The Event Bus enables Kyma to integrate with various other external solutions. The integration uses the publish-subscribe messaging pattern that allows Kyma to receive business Events from different solutions, enrich the events, and trigger business flows using lambdas or services defined in Kyma. See the Event Bus documentation.

Docker Images

Currently, Event Bus makes the following three Docker images available to the kyma core Helm chart:

• event-bus-publish
• event-bus-push
• event-bus-sub-validator

There are also end-to-end test Docker images to use as helm tests. See the tests in the event-bus directory for more details.

Development

The three binaries of Event Bus reside under cmd/event-bus-XXXX "e.g. cmd/event-bus-publish". They each have a Makefile to build and test the component as well as to create and push a Docker image. The following table explains the various make targets.

Command	Description
make	This is the default target for building the Docker image. It tests, compiles, creates, and appropriately tags a Docker image.
make build	Runs all the tests and the linter. It compiles the binary in the bin directory.
make push	Pushes the Docker image to the registry specified in the REGISTRY variable of the Makefile.
make docker-build	Creates a Docker image.
make test	Run all the tests.
make vet	Runs go vet on all sources including vendor but excluding the generated directory.
make compile	Builds a binary without running any tests.