Make check_active name more generic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steven Hardy |
Bug Description
As mentioned in https:/
I think we need to consider revising the check_active interface to make it more generic - I've been running into issues trying to use the same check_active pattern for non-active transistions, e.g stack-suspend without adding more check_foo functions to the plugin API
I think it would be better if we had check_status(self, thing_checking_
while not self.check_
yield
The advantages of this:
One check interface function in the plugin API, should be more flexible and less fragile than an expanding list of check_foo functions?
Aligns the top-level states we're checking for with the actual state of the resource (e.g self.CREATE_
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steven Hardy (shardy) |
milestone: | none → havana-1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | havana-1 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/28781
Review: https:/