yahoo-eng-team team mailing list archive

[Adrian Turjak <adriant@xxxxxxxxxxxxxxx>]

Public bug reported:

DEFAULT_SERVICE_REGIONS makes it sound like it is setting default
regions when a services_region cookie isn't present, when in fact it
takes precedence over a cookie.

This is terrible UX because a user that can change to another valid
region is forced on login to the region always defined in
DEFAULT_SERVICE_REGIONS, and then always change manually to the region
they want every time.

The cookie, a user controlled value, should always take precedence over
a 'default' value. If we want to allow a forceful override then it
should be called something else such as FORCED_SERVICE_REGIONS.

The settings don't even make this behavior clear, which further makes me think this is a bug or an unconsidered part of the implementation:
https://docs.openstack.org/horizon/latest/configuration/settings.html#default-service-regions


We should change the precedence to:
1. services_region cookie
2. DEFAULT_SERVICE_REGIONS endpoint
3. any valid region from the catalog

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1772345

Title:
  DEFAULT_SERVICE_REGIONS overrides services_region cookie

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  DEFAULT_SERVICE_REGIONS makes it sound like it is setting default
  regions when a services_region cookie isn't present, when in fact it
  takes precedence over a cookie.

  This is terrible UX because a user that can change to another valid
  region is forced on login to the region always defined in
  DEFAULT_SERVICE_REGIONS, and then always change manually to the region
  they want every time.

  The cookie, a user controlled value, should always take precedence
  over a 'default' value. If we want to allow a forceful override then
  it should be called something else such as FORCED_SERVICE_REGIONS.

  The settings don't even make this behavior clear, which further makes me think this is a bug or an unconsidered part of the implementation:
  https://docs.openstack.org/horizon/latest/configuration/settings.html#default-service-regions

  
  We should change the precedence to:
  1. services_region cookie
  2. DEFAULT_SERVICE_REGIONS endpoint
  3. any valid region from the catalog

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1772345/+subscriptions