yahoo-eng-team team mailing list archive

[Henry Nash <henryn@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Commit ad7a7bd6ee36a7af61f88d98038d83aba25a9743
(https://review.openstack.org/#/c/296140/) moved driver interfaces for
core Identity into their own module (base.py in the backend directory).
For compatibility it included a class definition of IdentityDriverV8 in
the original location (core.py), with a deprecation warning.

@versionutils.deprecated(
    versionutils.deprecated.MITAKA,
    what='keystone.identity.IdentityDriverV8',
    in_favor_of='keystone.identity.backends.base.IdentityDriverV8',
    remove_in=+1)
class IdentityDriverV8(identity_interface.IdentityDriverV8):
    pass

There appear to be two things wrong with this:

1) I don't believe this merged for Mitaka. Hence we can't retrospectively start the deprecation in Mitaka
2) I thought we were committing to 2 cycles for deprecation in general.

Hence I think this should be NEWTON + 2.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
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/1569814

Title:
  Incorrect deprecation warning for IdentityDriverV8

Status in OpenStack Identity (keystone):
  New

Bug description:
  Commit ad7a7bd6ee36a7af61f88d98038d83aba25a9743
  (https://review.openstack.org/#/c/296140/) moved driver interfaces for
  core Identity into their own module (base.py in the backend
  directory). For compatibility it included a class definition of
  IdentityDriverV8 in the original location (core.py), with a
  deprecation warning.

  @versionutils.deprecated(
      versionutils.deprecated.MITAKA,
      what='keystone.identity.IdentityDriverV8',
      in_favor_of='keystone.identity.backends.base.IdentityDriverV8',
      remove_in=+1)
  class IdentityDriverV8(identity_interface.IdentityDriverV8):
      pass

  There appear to be two things wrong with this:

  1) I don't believe this merged for Mitaka. Hence we can't retrospectively start the deprecation in Mitaka
  2) I thought we were committing to 2 cycles for deprecation in general.

  Hence I think this should be NEWTON + 2.

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