GitLab

- Introduce a new GET endpoint for listing listener history in the WAF router.
- Implement ListListenerHistory method in the WafController to handle requests and return paginated results based on query parameters.
- Enhance the WAF service to log listener creation and deletion events, capturing relevant details for auditing purposes.
- Update the WafListenerHistory model and service methods to support querying and storing listener history data effectively.

- Introduce ListWafs method in WafController to retrieve a list of WAF services
- Update WAF router to include new GET routes for listing WAFs
- Implement ListWafs method in the service layer to fetch WAF data from the database
- Enhance the MatcherExpr and WafService structures to support new functionality

- Implement Create, Update, Enable, Delete, and Get methods for managing Black/White Lists
- Introduce new routes in the WAF router for handling Black/White List operations
- Update service and model layers to support new functionality
- Refactor cluster client management to accommodate new Kubernetes client structure

- Remove leading slash from v2 WAF API route paths
- Ensure consistent route path formatting

- 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

- Uncomment and activate AuthMiddleware in router configuration
- Add conditional skip for ping endpoint in authentication middleware
- Restore authentication checks for both release and debug modes

- 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

- Modify WAF route to use empty string for root path
- Remove commented-out route for gateway endpoint
- Simplify route configuration in `SetWafRouter`

- Remove path parameters from route configuration
- Align with previous changes to use query-based parameter retrieval

- Update WAF router configuration to use POST method for enabling multiple listeners
- Maintain consistency with other WAF-related API endpoint HTTP methods

- 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