Individual operation mode for each endpoint

[0x566164696D]

In most cases, it is not possible to immediately launch API-Firewall in BLOCK mode; we have to start in monitoring mode, analyze logs, and make changes to the OAS, which takes quite a lot of time.
Moreover, it is inconvenient to roll out API updates in BLOCK mode.

Is it possible to implement individual management of the operation mode for each endpoint?

Examples:
We launched API-Firewall in LOG_ONLY mode, identified endpoints without errors, and enabled BLOCK for them, thus gradually transitioning the entire API to BLOCK mode.

With such a configuration, it is also possible to safely deploy new API endpoints (they will be in LOG_ONLY) and switch them to BLOCK when ready.

It is preferable for the operation mode to be set not in the specification but, for example, through an additional config.

[ericung]

I don't understand the solution completely, however, if we add another additional config will it make the application file system too complicated for someone to pick up? Can't we add an option to the existing configuration files? The docker-compose.yml file in the docs is simple right now so someone new to the solution can pick it up, however, I understand that when api-firewall goes into production, more configuration options are added to the mix inside this particular file. In short, can't we just keep it simple and put it somewhere easy to reach for everyone?