project-id-required-as-root

Currently, it appears one must have a project ID set, even when acting as root creating projects. Observe:

$ curl -X POST http://127.0.0.1:8080/v1/projects -H "Content-Type: application/json" -H "X-Auth-Token: bootstrap" -H "X-Auth-User: bootstrap" -d '{"name": "test1"}'
{"message": "Project ID ('None') is not a valid UUID"}

When acting at this level, there's no reason to supply a project ID because you're not relating your requests to any in particular.

This is equally confusing when you use a separate project ID from the one you're querying. Observe:

$ curl http://127.0.0.1:8080/v1/projects/c03bb45c-3799-4f5d-82d0-307def88a220 -H "Content-Type: application/json" -H "X-Auth-Token: bootstrap" -H "X-Auth-User: bootstrap" -H "X-Auth-Project: b9f10eca66ac4c279c139d01e65f96b4"
{"created_at": "2017-02-02T20:55:24.000000", "id": "c03bb45c-3799-4f5d-82d0-307def88a220", "name": "test1", "updated_at": null, "variables": {}}

Note that the project ID in the header does not correspond to the project ID in the URL.