Sverre H. Huseby

icon location Oslo, NO icon location 1st Sun-certified Java-dev in Norway ('97). Spent some years teaching other devs that security is their business. Born coder. Will die a coder. Karate-nerd.

Results 23 comments of Sverre H. Huseby

Blocker: @Column fields do not get reset to null

We were bitten by this one as well, as we expected any change we did to the entities (including setting fields to null) to be reflected in the database. I...

ansible galaxy install collection from git replaces directory symlinks with empty dir

Is anyone preparing a PR for this?

ansible galaxy install collection from git replaces directory symlinks with empty dir

> If it can be useful I was giving a quick look at it and trying to develop a test for the specific use case to cover it Would be...

Missing data in prometheus scrapes

As #63 is now closed, I guess this one may be closed too?

Kafka Lag Exporter container fails with PKCS12 certificates when generated with JDK17

Is this still an issue, now that the container uses Java 17? I suggest closing it.

Change docker base image due to security findings

I suggest closing this issue. The base image has been changed (at least) twice since it was reported.

Can we configure any other kafka principal user instead of kafka-lag-exporter as in my kafka environment not able to create new principal user due to restricted access

I suggest closing this issue, as there have been many months without any clarifications to the question.

Separate trustore/keystore creation for multple service in the same host

> `failure 1 during daemon-reload: Failed to connect to bus: No such file or directory\n` I had the same problem on my Mac just now, and got past it by...

chore: misc updates and improvements made while you were gone, take 2

Hi, @purbon! As noted in the description, the tests will continue to fail for this PR (and others) as long as [the previous merge to `master`](https://github.com/kafka-ops/julie/pull/581) is not reverted or...

Fix: CLI integration tests do not use correct credentials and broker port

This still breaks the unit tests. There is no broker at localhost:909x when unit tests are run. Maybe you could disable your functionality during dry-run, if that makes any sense?...