Error with connectors block
See original GitHub issueDeploying like this will cause an error:
---
team: "planetexpress"
source: "source"
projects:
- name: "natas"
consumers:
- principal: "User:Bender"
- principal: "User:Fry"
- principal: "User:Lila"
producers:
- principal: "User:Fry"
- principal: "User:Lila"
connectors:
- principal: "User:Connect1"
topics:
read:
- "topicA"
- "topicB"
- principal: "User:Connect2"
topics:
write:
- "topicC"
- "topicD"
topics:
- name: "foo"
config:
replication.factor: "1"
num.partitions: "1"
- dataType: "avro"
name: "bar"
config:
replication.factor: "1"
num.partitions: "1"
rbac:
- ResourceOwner:
- principal: "User:Professor"
- DeveloperManage:
- principal: "User:Zoidberg"
However removing the connectors block will work.
kafka-topology-builder.sh --brokers localhost:9093 --clientConfig topology.properties --topology topology_docs.yaml
log4j:WARN No appenders could be found for logger (org.apache.kafka.clients.admin.AdminClientConfig).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Exception in thread "main" java.lang.NullPointerException
at com.purbon.kafka.topology.api.mds.MDSApiClient.getClusterIds(MDSApiClient.java:202)
at com.purbon.kafka.topology.roles.AdminRoleRunner.forKafkaConnect(AdminRoleRunner.java:54)
at com.purbon.kafka.topology.roles.RBACProvider.setAclsForConnect(RBACProvider.java:61)
at com.purbon.kafka.topology.AccessControlManager.syncApplicationAcls(AccessControlManager.java:157)
at com.purbon.kafka.topology.AccessControlManager.lambda$sync$2(AccessControlManager.java:107)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at com.purbon.kafka.topology.AccessControlManager.lambda$sync$3(AccessControlManager.java:105)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at com.purbon.kafka.topology.AccessControlManager.sync(AccessControlManager.java:74)
at com.purbon.kafka.topology.KafkaTopologyBuilder.run(KafkaTopologyBuilder.java:87)
at com.purbon.kafka.topology.BuilderCLI.processTopology(BuilderCLI.java:154)
at com.purbon.kafka.topology.BuilderCLI.main(BuilderCLI.java:118)
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Connection Error: Office365user is in the block list
The user is on the 'block list', but the user has a complete office account. Full text: "Runtime call was blocked because connection...
Read more >Question: Http client connector error code in catch block
Dear All, Can any one tell me how can i get the http connector error message in catch block notify shape? i tried...
Read more >Solved: ErrorMode 0 blocks script errors from Connectors?
Unfortunately, when using a Connector no more error details are passed to the script when ErrorMode equals 0. It seems as if everything...
Read more >Block Connector access in Power Platform Admin Center
Here's how you can block Connectors or their Actions using Data Policies in Power Automate Admin Center.
Read more >Connectors and Terminal Block Types: Uses & Wiring
Terminal blocks come in a range of shapes, sizes and ratings, but always terminate a single wire (single pole) and are never multi-pole....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Fobhep I will investigate, but when #49 is merged all will be good.
ah sorry - me being trigger happy 😄