Expose trigger_rules functionality in authservice config
Feature request!
When keycloak protection is enabled at the gateway level, it can be difficult (or impossible) to disable for specific URLs. Authservice trigger rules could be used to configure path matching exceptions (among other use cases) to authservice enforcement.
This could be useful in many situations for debugging authservice/keycloak configuration, or simply exposing specific endpoints which do not require keycloak authentication (as is the case in some deployments).
In order to enable support through bigbang configuration, I believe updates would need to be made to the authservice secret.