GitLab

- Integrate Elasticsearch client for querying WAF attack logs
- Add new API endpoints for listing attack logs and WAF rules
- Implement pagination and filtering for attack log retrieval
- Support language-based rule category display
- Update service and controller layers to support new functionality

- 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

- Extend CreateWafReq and EnableListenerWafReq structs with Mode field
- Update CreateWaf method to use requested WAF mode
- Modify EnableListenerWafs to retrieve and apply WAF mode from existing service
- Ensure mode is consistently passed through WAF service operations

- Modify `WafService` struct to include listener information
- Update `GetWaf` method to retrieve and format listener details
- Enhance `ListListenerWafStatus` to return hosts for each listener
- Remove commented-out code and unused port list logic

- Modify `ListenerWaf` struct to use single `HostsAndPort` field instead of separate `Hosts` and `Port`
- Update `EnableListenerWafsReq` to use `ListenerWaf` slice for listeners
- Change `waf_services` table migration to use `BIGINT` and `AUTO_INCREMENT`
- Adjust `EnableListenerWafs` method to parse new listener format
- Add logging for listener name during WAF configuration

- Added `Name` field to `ListenerWaf` struct in `internal/service/types.go`
- Updated Go module dependencies, adding Elasticsearch client library
- Removed `CreateListener` method from `waf.go` service

- Updated `EnableListenerWafsReq` struct to use string slice for listeners
- Modified WAF service method to parse listener string into hosts and port
- Simplified listener WAF configuration logic to work with new listener representation
- Added error handling for port parsing and listener format validation

- 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

- Modified SQL migration to add 'hosts' column to gateway_listeners table
- Updated model, service, and controller to support hosts in gateway listener operations
- Added new GetWafGatewayInfo method to retrieve WAF gateway information
- Refactored WAF service methods to handle hosts and improve flexibility