Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/277
@neykov interesting discussion. The "validConditions" makes a lot of sense.
I was imagining we'd list abortConditions as {on-fire, stopping, stopped,
destroyed} (which is quite verbose compared to your `validConditions`).
I also like the idea of being able to assert about a different sensor. We
can do that in the Java code's `DependentConfiguration` (unrelated, but I used
that as inspiration). It's a bit more fiddly to wire in here.
I'm going to leave in the `abortConditions`, and think about adding
`validConditions` as well (in a different PR). My one concern about
`validConditions` is that it sounds like it could be a valid termination
condition, rather than us keeping going until the assert succeeds.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---