GitLab

Update WAF API routing to remove wildcard from attack log endpoint, enhancing clarity and consistency in log proxy handling.

Refactor WAF API routing and configuration to streamline endpoint structure and enhance clarity. Update region configuration to include WAF API server details, improving integration with the WAF controller.

Refactor WAF routing to use SetWafApiServerRouter function, improving API server integration and configuration handling.

Enhance WAF detection event structure in LogConsumerService by adding action and request details in a nested format. This refactor improves clarity and context for generated events, facilitating better analysis of detected attacks.

Refactor API router and WAF handling to support additional parameters and improve configuration management

This update modifies the SetRouters and SetWafRouter functions to accept new parameters, including a debug flag and a region URL map, enhancing the flexibility of the API routing. Additionally, a new SetApiRouters function is introduced for better organization of API routes. The configuration management has been streamlined by moving configuration imports to the internal package, ensuring a more consistent structure across the application.

- Introduce ListWafsV2 method in WafController to enhance the WAF listing functionality with a new response structure.
- Update the API route for listing WAFs to point to the new ListWafsV2 method, improving clarity and consistency in the API design.

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

- 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

- 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