Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Topologies from different teams

See original GitHub issue

The topology builder won’t allow topologie files for different teams when using the “dir” option, ie specifying a directory path with the --topology flag. Being able to use that however- would be imho highly useful.

Exception in thread "main" java.io.IOException: Topologies from different teams are not allowed
        at com.purbon.kafka.topology.KafkaTopologyBuilder.buildTopology(KafkaTopologyBuilder.java:101)
        at com.purbon.kafka.topology.KafkaTopologyBuilder.run(KafkaTopologyBuilder.java:78)
        at com.purbon.kafka.topology.BuilderCLI.processTopology(BuilderCLI.java:154)
        at com.purbon.kafka.topology.BuilderCLI.main(BuilderCLI.java:118)

EDIT: When applying single topolgy files for different teams it won’t work neither - only the first file will be “executed”

Issue Analytics

State:
Created 3 years ago
Comments:14 (7 by maintainers)

Top GitHub Comments

1reaction

Fobhepcommented, Dec 7, 2020

@purbon any updates on this? It would be really awesome if once could manage that KTB is only allowed to delete topics that belong to your current context!

1reaction

purboncommented, Jul 3, 2020

This is an expected behaviour, end of the day we need to group the different topologies under the same roof, so i used the first key (aka teams). This key is named teams, but could actually be named differently, end of the day is a bigger umbrella to the project level, this might be teams based on my experience.

Remember, after team and until project, you can pull in any key, value pair, and the values will be in between teams value and the project name at the end in the topic.

Top Results From Across the Web

Key Concepts - Team Topologies

Four fundamental topologies · Stream-aligned team: aligned to a flow of work from (usually) a segment of the business domain · Enabling team:...

Team Topologies | Atlassian

Leaders immensely benefit from looking through the lens of Team Topologies. Learn how four fundamental team topologies influence a DevOps transformation.

Team Topologies: Organizing Business and Technology ...

Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team...

5 Keys to Successfully Implement Team Topologies in Your ...

Team Topologies proposes an organizational design encompassing four teams. This separation is guided by the principle of having teams that ...

Organizing Agile Teams and ARTs: Team Topologies at Scale

This contrasts with traditional component teams, which may be justified for other good reasons, such as reuse or architectural integrity. As a ...