Removal of Resource.metadata attribute not backwards compatible

Bug #1324704 reported by Steve Baker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
High
Steve Baker

Bug Description

Resource.metadata should be restored, but using it should log a deprecation warning

Changed in heat:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Steve Baker (steve-stevebaker)
milestone: none → juno-1
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/96618

Changed in heat:
status: Triaged → In Progress
Thierry Carrez (ttx)
Changed in heat:
milestone: juno-1 → juno-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

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

commit 19a8dbfa5ffb6467fd6abeb76afb4c6f7997044e
Author: Steve Baker <email address hidden>
Date: Fri Jun 13 12:49:52 2014 +1200

    Restore resource metadata attribute

    For backwards compatibility the Resource.metadata attribute
    has been restored, however reading or assigning this attribute
    will result in a deprecation warning.

    Reading metadata will force a refresh from the database, which
    maintains the previous behaviour rather than optimising for
    performance.

    Change-Id: Ifdcf3d98b99a09aac8755c84ef3f59d8602fc6a8
    Closes-Bug: #1324704

Changed in heat:
status: In Progress → Fix Committed
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: juno-2 → 2014.2
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.