GitLab

- Introduce new API routes for fetching attack log details and response packages.
- Implement corresponding methods in the WafController and wafService to handle the new functionality.
- Update service interface and types to support the new data structures for attack logs and responses.

- 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.

- Introduce a new GET endpoint for listing attack classes in the WAF router.
- Implement AttackClassesList method in WafController to handle requests and return attack class data based on the specified language.
- Enhance the WAF service with ListAttackClasses method to retrieve attack classes and support localization for descriptions.
- Define AttackClasses struct to standardize the response format for attack class data.

- 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

- Correct the field name from 'Catagory' to 'Category' in WafRuleCategory struct
- Update references in SaveRuleCategoryToDB method to reflect the corrected field name
- Ensure consistency in category naming across the WAF service

- Extend CreateWafReq struct with ServiceID field
- Update CreateWaf method to include ServiceID in WAF configuration
- Implement getServiceID method to retrieve or create WAF service
- Modify EnableListenerWaf to handle ServiceID retrieval and creation
- Ensure consistent WAF service tracking across different operations

- 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