GitLab

- Update the GetBlackWhiteLists method in both the service and controller layers to return the total number of items alongside the list of MatcherExpr.
- Modify response structure in the controller to include total items for improved client-side handling.
- Ensure proper error handling and maintain existing functionality while enhancing data retrieval capabilities.

- Update the database operation in the EnableBlackWhiteList method to use Model and Where clauses for a more precise status update.
- Improve the clarity and efficiency of the database interaction within the WAF service.

- Introduce a condition to prevent unnecessary operations if the requested status matches the current status in the EnableBlackWhiteList method.
- Enhance the efficiency of the WAF service by avoiding redundant updates.

- Modify the updateConfigMap method to replace the scope with gateway names instead of IDs
- Enhance the handling of WAF service configurations for improved clarity and functionality

- Add UpdateBlackWhiteList method in WafController to handle updates to black/white list entries
- Introduce EnableBlackWhiteList method in WafController for enabling/disabling black/white lists
- Enhance WafService with logic to update and manage configuration maps for black/white lists
- Ensure proper error handling and response assembly for both methods

- 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

- 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

- Introduce a new response structure to encapsulate rule group items
- Map existing rules to the new response format, including category details
- Ensure consistent response format for improved API usability

- 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 console writer to log output for improved readability
- Maintain debug log level configuration

- Change zerolog global log level from Info to Debug
- Improve visibility into application startup and runtime behavior

- Add number decoder to Elasticsearch client configuration
- Ensure proper parsing of numeric fields in Elasticsearch responses

- 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

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

- 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

- Modify HTTP request method in AuthMiddleware from POST to GET
- Ensure compatibility with SSO service authentication endpoint

- Log specific SSO authentication error code and message
- Improve error traceability and debugging for authentication middleware

- Add timeout and TLS configuration to HTTP client in AuthMiddleware
- Enable insecure TLS connection for SSO service requests
- Log errors for failed SSO authentication requests
- Improve error handling and network resilience in authentication process

- Integrate zerolog for detailed error logging in AuthMiddleware
- Log errors when reading SSO response body or unmarshaling response
- Improve error traceability during authentication process

- 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

- 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

- 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` method in WafController to retrieve gateway details using query parameters
- Modify parameter extraction from `ctx.Param()` to `ctx.Query()`
- Maintain consistent method signature and service call logic

- Add `Code`, `Message`, and `StatusCode` fields to `SuccessResponse` and `FailResponse`
- Remove `RespErr` struct and directly include error details in `FailResponse`
- Modify `AssembleResponse` to use new response structure with standardized fields