GitLab

- Introduce a label to the ConfigMap for black/white list to enhance identification and management
- Add logging for the ConfigMap name to improve visibility during configuration creation

- Introduce logging of svcMap to provide better visibility into service mapping during Black/White List creation
- Enhance debugging capabilities for the WAF service operations

- 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 ListRules method to handle English and Chinese categories
- Append appropriate category names and descriptions based on selected language
- Ensure consistent response structure for rule group responses

- Update condition to check for nil RuleCategoryStatus before accessing Status
- Ensure safe handling of WAF service rule categories

- Set the global configuration variable Conf to enable Debug mode
- Include UUID in the attack log structure for better identification of WAF detections

- 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

- Adjust time range filtering to use strictly positive time values
- Rename Elasticsearch query result variable for improved readability
- Maintain existing logging and error handling for WAF attack log retrieval

- Add log statements to track Elasticsearch query hits and source data
- Improve visibility into WAF attack log retrieval process
- Log raw Elasticsearch response and individual hit sources for debugging

- Update log level for WAF detection query source logging
- Improve visibility of Elasticsearch query source information

- 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

- Add direct mode assignment to listener specification
- Ensure listener mode is updated during concurrent processing
- Simplify mode update logic in UpdateMode method

- Add synchronization mechanism using sync.WaitGroup
- Implement concurrent goroutine updates for WAF service listeners
- Ensure all listener updates complete before returning
- Create local listener variable to prevent goroutine closure issues

- Implement concurrent listener mode updates for WAF services
- Add client retrieval and listing of listeners by gateway name
- Return updated WAF service metadata after mode modification
- Improve error handling for client and listener operations

- Add error logging for listener list retrieval
- Modify host extraction to use substring before port separator
- Improve error handling and logging in WAF service method

- Commented out database operations in `EnableListenerWaf` method
- Simplified WAF creation and deletion logic using request parameters
- Removed `host` column from `waf_services` table migration
- Updated logging to use request parameters instead of listener object

- 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 comment to clarify port extraction from `HostsAndPort` field
- Improve code readability by updating inline documentation

- 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

- Improve CreateWaf method by adding validation for rule count
- Update error messages in cluster client retrieval
- Return WafService struct with basic metadata on successful creation
- Remove commented-out legacy code
- Enhance error handling in DeleteListenerWaf and CreateWaf methods

- 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 config loading in `cmd/app/config.go` to use JSON instead of YAML
- Modified `internal/service/waf.go` to read WAF rules from JSON file
- Removed YAML library imports and replaced with JSON unmarshaling
- Updated file extensions from `.yaml` to `.json` in file reading logic

- 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

- Added log statements to help debug API Gateway listener list retrieval
- Logs the raw response and parsed response for troubleshooting purposes

- 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