LogDog: Add prefix registration endpoint.

appengine/cmd/logdog_coordinator/register/module-register.yaml

Index: appengine/cmd/logdog_coordinator/register/module-register.yaml
diff --git a/appengine/cmd/logdog_coordinator/services/module-services.yaml b/appengine/cmd/logdog_coordinator/register/module-register.yaml
similarity index 93%
copy from appengine/cmd/logdog_coordinator/services/module-services.yaml
copy to appengine/cmd/logdog_coordinator/register/module-register.yaml
index 7fe5777a4c824d9ddf648277ee5f981ccfd1c0e7..0acaa653c43860d621f6219d5f8bc4482897f29e 100644
--- a/appengine/cmd/logdog_coordinator/services/module-services.yaml
+++ b/appengine/cmd/logdog_coordinator/register/module-register.yaml
@@ -2,7 +2,7 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-module: services
+module: register

[nodir, 2016/05/19 16:43:17]

I am not sure why you have to have a whole another appengine module for one
function. Why not same module? Why not same service? looks unnecessarily
complicated to me

[dnj (Google), 2016/05/19 22:52:04]

Well, currently I have the following modules:
"backend": Specifically backend services, admin/cron only.
"vmuser": A *managed VM* instance for user access.
"service": A classic GAE instance for only service access.

My thought was that all of these share ACL sets, so I'd create another separate
module space for the new ACL set (write). However, I guess I had a "one module
per service" mentality. I think I will put this into the "service" endpoint and
just have it export two services.

 runtime: go
 api_version: go1