You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chip Ingress Set is a composite component that collects Beholder events. It is a thin `testcontainers-go` wrapper over a Docker Compose file copied from the [Atlas](https://github.com/smartcontractkit/atlas/blob/master/chip-ingress/docker-compose.yml) repo.
Where compose file indicates the location of the `docker-compose.yml` file (remote URLs are supported) and `extra_docker_networks` an optional slice of existing Docker networks, to which whole stack should be connected to.
20
+
21
+
## Exposed ports
22
+
23
+
These 3 components expose a variety of ports, but the most important ones from the point of view of user interaction are:
24
+
- schema registry port: `18081`
25
+
- Kafka port: `19092`
26
+
- Red Panda console port: `8080`
27
+
28
+
## Useful helper methods
29
+
30
+
Packge contains also a bunch of helper functions tha can:
31
+
- create and delete Kafka topics
32
+
- fetch `.proto` files from remote repositories and register them with Red Panda
Registration logic is very simple and should handle cases of protos that import other protos as long they are all available in the `ProtoSchemaSet`s provided to the registration function. That function uses an algorithm called "topological sorting by trail", which will try to register all protos in a loop until it cannot register any more protos or it has registered all of them. That allows us to skip dependency parsing completely.
115
+
116
+
Since Kafka doesn't have any automatic discoverability mechanism for subject - schema relationship (it has to be provided out-of-band) code currently only knows how to correctly register protos from [chainlink-protos](https://github.com/smartcontractkit/chainlink-protos) repository.
0 commit comments