Is your feature request related to a problem? Please describe.
Since Orion 4.3.0 Kafka based Notifications are supported and the new data persistence system kafnus (replacement for cygnus) needs them. So FiLiP should also support this to enable working with it.
Describe the solution you'd like
The Notification model needs to be expanded by kafka and kafkaCustom in the same schema like http and mqtt.
Describe alternatives you've considered
There is no alternative because it is based on kafka, so the only other solution would be not using FiLiP.
Additional context
We need to set the following fields at kafkaCustom (see orion-api section):
- url
- topic
- key
- user
- passwd
- saslMechanism
- securityProtocol
Is your feature request related to a problem? Please describe.
Since Orion 4.3.0 Kafka based Notifications are supported and the new data persistence system kafnus (replacement for cygnus) needs them. So FiLiP should also support this to enable working with it.
Describe the solution you'd like
The Notification model needs to be expanded by
kafkaandkafkaCustomin the same schema like http and mqtt.Describe alternatives you've considered
There is no alternative because it is based on kafka, so the only other solution would be not using FiLiP.
Additional context
We need to set the following fields at
kafkaCustom(see orion-api section):