Adding a second region breaks existing clients

[Sam Morrison]

We currently have an installation with a single region. We want to expand to another region but this is proving difficult.

When I add a new endpoint for our new region, clients that are configured not to use a region can (depending on the ID of the endpoint) all of a sudden now start hitting the new endpoint.

It is not practical to get all of our thousands of users using lots of different clients to explicitly set a region when authing.

So I'm wondering if it is possible to support a default region or default endpoint. This endpoint would be listed first when listing the endpoints for a service. Currently this is ordered based on the endpoint ID so a work around is to hack the endpoint IDs to ensure the one you want listed first is set.

Thoughts?

[Adam Young (ayoung)]

Would the default be per user, per project, per domain, or just on the server if not explicitly set?

Would a config option be required?

[Sam Morrison (sorrison)]

For us a global default region would suffice, could be done with a config option or maybe be an attribute of a region (eg. default=true)