yahoo-eng-team team mailing list archive

[Henry Nash <henryn@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There are a few cases where, for backward compatibility, we honor older
config values to ensure that installations don't break on upgrade
between releases.  A good example of this is the 'driver' config setting
from when we split up the original identity manager/backend - as well as
the config values around the new spit of assignment.

We should issue deprecation warnings when the new config values have not
been set and the old one still are set (in which case we use the old
values).  However, the current versionutils.deprecated class doesn't
really support the logging of arbitrary objects (it supports just
classes and functions).  This should be enhanced, and then places where
we do provide this backward compatibility for config values should be so
marked (The __init__ method in the manager class for resource/core.py
and assignment/core.py are good places to start).

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1393365

Title:
  cross-manager use of config values for backward compatibility should
  have deprecation warnings

Status in OpenStack Identity (Keystone):
  New

Bug description:
  There are a few cases where, for backward compatibility, we honor
  older config values to ensure that installations don't break on
  upgrade between releases.  A good example of this is the 'driver'
  config setting from when we split up the original identity
  manager/backend - as well as the config values around the new spit of
  assignment.

  We should issue deprecation warnings when the new config values have
  not been set and the old one still are set (in which case we use the
  old values).  However, the current versionutils.deprecated class
  doesn't really support the logging of arbitrary objects (it supports
  just classes and functions).  This should be enhanced, and then places
  where we do provide this backward compatibility for config values
  should be so marked (The __init__ method in the manager class for
  resource/core.py and assignment/core.py are good places to start).

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