Improve compatibility between Keystone V2 and V3 interfaces

Bug #1289528 reported by andersonvom
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Richard Lee

Bug Description

Both heat Keystone client implementations have @properties that point to self.client_v2 and self.client_v3, respectively. To improve compatibility with their interfaces, they should just be called self.client, to allow them to be switched in a more seamless manner.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/79053

Changed in heat:
assignee: nobody → andersonvom (andersonvom)
status: New → In Progress
Steven Hardy (shardy)
Changed in heat:
milestone: none → icehouse-rc1
importance: Undecided → Medium
Changed in heat:
assignee: andersonvom (andersonvom) → Richard Lee (rblee88)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/79053
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=d96398aaa0d7094177875e4ef713b68ac4cfa6b2
Submitter: Jenkins
Branch: master

commit d96398aaa0d7094177875e4ef713b68ac4cfa6b2
Author: Anderson Mesquita <email address hidden>
Date: Fri Mar 7 13:01:28 2014 -0600

    Improve compatibility between Keystone V2 and V3

    To improve compatibility between Keystone V2 and V3, this renames the
    client @property in both of them from self.client_v2 and self.client_v3
    to just self.client.

    This allows both of them to be used by third party contrib plugins in a
    seamless manner.

    Closes-Bug: 1289528
    Co-Authored-By: Richard Lee <email address hidden>
    Change-Id: I60412ecb1665232ffeeeb869fb00d368604601d2

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: icehouse-rc1 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.