s3 and swift resources don't upcall in validate

Bug #1260643 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Low
Thomas Herve

Bug Description

Both S3Bucket and SwiftContainer contain (useless) validate methods method which don't call Resource.validate, thus not validating properties when doing a Stack.validate. It doesn't create a big problem because we do an additional properties.validate when actually creating the resource, but making the call earlier gives a better error.

Those methods should be removed as they don't provide any value (we already conditionally register them).

Changed in heat:
milestone: none → icehouse-2
status: New → Triaged
Thomas Herve (therve)
Changed in heat:
assignee: nobody → Thomas Herve (therve)
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/62394

Changed in heat:
status: Triaged → In Progress
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-2 → 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.