This change updates the dispatch.yml rules that impact how /v2/* requests are routed to the locate and locate-platform services. This change is step 3 of https://github.com/m-lab/dev-tracker/issues/600
Currently monitoring requests issued to /v2/platform/monitoring are actually routed to the "locate" service. This change ensures that those requests are delivered to the locate-platform service.
This change is necessary to allow us to manage the user-visible APIs in the locate service using Cloud Endpoints (e.g. /v2/nearest), without exposing users to extraneous API calls needed to manage the platform (e.g. monitoring).
This change updates the dispatch.yml rules that impact how
/v2/*requests are routed to the locate and locate-platform services. This change is step 3 of https://github.com/m-lab/dev-tracker/issues/600Currently monitoring requests issued to
/v2/platform/monitoringare actually routed to the "locate" service. This change ensures that those requests are delivered to the locate-platform service.This change is necessary to allow us to manage the user-visible APIs in the locate service using Cloud Endpoints (e.g. /v2/nearest), without exposing users to extraneous API calls needed to manage the platform (e.g. monitoring).
This change is