On Wed, 13 Jan 2016, Sean Dague wrote:
Because this regex is built from a dictionary, hash seed matters, and it
is not stable which will get precedence.
Ow[1].
I'd like to propose for Nova we restrict project_id in the URL to
[0-9a-f]+, which is any valid hex string. Ints are a subset of
As a note, there is potential that this will require older deployments that
have historical names migrated to update project IDs to hex-strings. These
are a minority of deployments at best, but this should be considered in the
proposal so if this goes forward we can clearly communicate this change
There is a snag at the moment in making project_id optional in API URLs
because of how python routes modules works.
When we call mapper.resource(...) it's creating a series of
mapper.connect(...) calls to setup routes. This just adds items to a
dictionary. When we later use the mapper to match a
On 01/13/2016 10:31 AM, Chris Dent wrote:
> On Wed, 13 Jan 2016, Sean Dague wrote:
>
>> Because this regex is built from a dictionary, hash seed matters, and it
>> is not stable which will get precedence.
>
> Ow[1].
>
>> I'd like to propose for Nova we restrict project_id in the URL to
>>
