rackerlabs/mimic

Refactor out Heat mimic's EventDescriptions

Opened this issue · 3 comments

Until multiple behaviors are needed by the heat mimic, the logic should be moved upwards.

glyph commented

I'm not sure I understand the issue here. "upwards"?

Right now, there is no point to grab the behavior registry collection and the pull the behavior from that, since there is only one behavior. "Upwards" refers to a less nested level, such as https://github.com/rackerlabs/mimic/blob/master/mimic/model/heat_objects.py#L249-L257 for stack creation. Behaviors can be added back in as they're needed.

glyph commented

Can stack creation / update not fail?