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.

Error with connectors block

See original GitHub issue

Deploying like this will cause an error:

team: "planetexpress"
source: "source"
  - name: "natas"
      - principal: "User:Bender"
      - principal: "User:Fry"
      - principal: "User:Lila"
      - principal: "User:Fry"
      - principal: "User:Lila"
      - principal: "User:Connect1"
            - "topicA"
            - "topicB"
      - principal: "User:Connect2"
            - "topicC"
            - "topicD"
      - name: "foo"
          replication.factor: "1"
          num.partitions: "1"
      - dataType: "avro"
        name: "bar"
          replication.factor: "1"
          num.partitions: "1"
      - ResourceOwner:
        - principal: "User:Professor"
      - DeveloperManage:
        - principal: "User:Zoidberg"

However removing the connectors block will work. --brokers localhost:9093 --clientConfig --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 for more info.
Exception in thread "main" java.lang.NullPointerException
        at com.purbon.kafka.topology.api.mds.MDSApiClient.getClusterIds(
        at com.purbon.kafka.topology.roles.AdminRoleRunner.forKafkaConnect(
        at com.purbon.kafka.topology.roles.RBACProvider.setAclsForConnect(
        at com.purbon.kafka.topology.AccessControlManager.syncApplicationAcls(
        at com.purbon.kafka.topology.AccessControlManager.lambda$sync$2(
        at java.util.ArrayList.forEach(
        at com.purbon.kafka.topology.AccessControlManager.lambda$sync$3(
        at java.util.ArrayList.forEach(
        at com.purbon.kafka.topology.AccessControlManager.sync(
        at com.purbon.kafka.topology.BuilderCLI.processTopology(
        at com.purbon.kafka.topology.BuilderCLI.main(

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

purboncommented, Jun 30, 2020

@Fobhep I will investigate, but when #49 is merged all will be good.

Fobhepcommented, Jun 29, 2020

ah sorry - me being trigger happy 😄

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found