You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: