s3 and swift resources don't upcall in validate
Bug #1260643 reported by
Thomas Herve
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 |
Changed in heat: | |
assignee: | nobody → Thomas Herve (therve) |
Changed in heat: | |
status: | In Progress → Fix Committed |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/62394
Review: https:/