yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

Marking as invalid. Validation should not vary based upon options set in
configuration keystone-to-keystone. It makes it hard to know what to
expect when interacting with keystone.

** Changed in: keystone
       Status: In Progress => Opinion

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

Title:
  Make validation patterns configurable

Status in OpenStack Identity (keystone):
  Opinion

Bug description:
  Keystone now treats configuration like a module, making it easier to
  enforce import order without race conditions[0]. There are a few TODOs
  to make certain validation patterns configurable. With the way
  configuration was being handled before, we were unable to import
  values from configuration on import. Now that configuration is
  referenced like a module-level package, we can avoid those race
  conditions. By making validation configurable we'll allow
  operators/deployers to choose how strict they wish to validate
  specific types [1][2].


  [0] https://github.com/openstack/keystone/commit/d9c6b50a3ae514e640fa13a344e59fe3649ee0ef
  [1] https://github.com/openstack/keystone/blob/46b76a3d8e302f47daf04c739066f70b7438e0da/keystone/common/validation/parameter_types.py#L42-L43
  [2] https://github.com/openstack/keystone/blob/46b76a3d8e302f47daf04c739066f70b7438e0da/keystone/common/validation/parameter_types.py#L62-L64

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