Inability to combine properties (masking definitions) between docker compose file and included config yml

[ivanbishop]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

When I define masking parameters in the docker compose and define my cluster there also, I see masking working on docker compose up via the UI. But, when I define my cluster in the compose file and instead include the masking commands in my configYML masking does NOT work (nor does it clock errors). Should I move my cluster definitions OUT of the docker compose file and into the configYML file? Attaching my compose file and configYML that DOES work on masking test_masking topic with a simple key "id"

Expected behavior

I expect if I define masking NOT in the compose file but instead in the extended config YML that it would work.

Your installation details

build: 9f79a56

cofigYML (1).txt
composeNEW (1).txt

Steps to reproduce

If I include my masking for key "id" in my launch docker compose I see masking. this works

 KAFKA_CLUSTERS_0_MASKING_0_TYPE: REPLACE
      KAFKA_CLUSTERS_0_MASKING_0_FIELDS_0: "id"
      KAFKA_CLUSTERS_0_MASKING_0_TOPICKEYSPATTERN: "test_masking.*"
      KAFKA_CLUSTERS_0_MASKING_0_TOPICVALUESPATTERN: "test_masking.*"

BUT, If i omit the masking from the compose file and instead try to combine with parameters in the config YML i.e.

kafka:
  clusters:
    - name: mycluster
      masking:
        - type: REPLACE
          fields: [ "id" ]
          topicValuesPattern: "test_masking.*"
          topicKeysPattern: "test_masking.*"

Doesnt work. no errors in log either

Screenshots

Logs

No response

Additional context

Happy to trouble shoot with team

[ivanbishop]

Any feedback here? Anything I can do to help?

[Haarolean]

Any feedback here? Anything I can do to help?

this is past triaging and is accepted, pending a fix by whoever wishes to/has time :)

[ivanbishop]

Any takers for this :) ? Outside my skill set unfortunately.