GitLab

- Simplify the update process for WAF service attack numbers by directly incrementing the attack_num field in the database.
- Remove redundant queries and error handling for improved code clarity and efficiency.
- Update attack log filter to clarify the purpose of the AttackApp field as the gateway name.
- Adjust the WAF service to correctly reference the gateway name in workload creation and modify attack log queries for consistency.

- Include informative log message when starting Kafka message consumption
- Enhance observability of log consumer service startup process

- Implement dynamic Kafka authentication mechanism (PLAIN/SCRAM)
- Add environment variable-based Kafka broker and authentication configuration
- Modify log consumer service to support flexible Kafka connection setup
- Update Elasticsearch store initialization with new index template
- Extend WAF service types to support listener name and hosts

- Add log consumer service to process WAF detection messages
- Implement message handling with JSON unmarshaling
- Save WAF detection logs to Elasticsearch
- Update WAF service attack number in database
- Modify ESStore to support bulk indexing with channel-based approach
- Add constants for Kafka topics and Elasticsearch indices

- Introduced new API endpoint and service method to enable/disable WAF for multiple listeners
- Updated router, controller, and service to support bulk listener WAF operations
- Added new request type `EnableListenerWafsReq` to handle multiple listener configurations
- Implemented logic to add or remove WAF configurations for specific listeners based on input