Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-4370

Improve handling of disabled features

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.4.0.GA
    • None
    • None
    • None

      In some situations, some parts of the User Operator are disabled. This includes:

      • ACL reconciliation when ACLs are disabled in the Kafka broker
      • SCRAM-SHA reconciliation in KRaft mode

      Currently, we create the operators for these resources as normal even when disabled. We just try to make sure in the code that they are not called. We should try to handle it better and avoid creating them. Two options come to my mind:

      • Not creating them at all and passing null instead of them. This would however trigger not exactly nice NPEs when called somewhere by mistake.
      • Create a dummy version of the operators which would just override all methods with some UnsupportedException => this would create a clear logging path when they would be called while the feature is disabled.

              Unassigned Unassigned
              scholzj JAkub Scholz
              Jan Kalinic Jan Kalinic
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: