Route path deep tree


Use case:
Service with the following route

And at this moment i set-up KONG path with the following path regex : /(?i)v1/Resource1
With that configuration, i have capabilities to access my services and these resources. But the team is continuous improving and creating new features and they decided to add a new sub-resource to their services but we don´t want to expose to our public consumers:

New: …/v1/Resource1/id/Resource2/id/Resource3

After the deployment of the service, everyone can access to the Resource 3 because the team forgets to update kong routes.

For these cases, what should be the best approach to avoid every resource / sub-resource to be available to our consumers.

Imagine that you have a lot of teams