From de6441712361323338cbfdccc2355e6ce1049824 Mon Sep 17 00:00:00 2001 From: Yujun Zhang Date: Wed, 7 Jun 2017 10:20:59 +0800 Subject: [PATCH] Add release note about entity equivalence Change-Id: Ifb297bff80fce37ae7b136e2aa3f211acb2a9097 Signed-off-by: Yujun Zhang --- .../notes/entity-equivalence-44c0da4cf3b5bc7e.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 releasenotes/notes/entity-equivalence-44c0da4cf3b5bc7e.yaml diff --git a/releasenotes/notes/entity-equivalence-44c0da4cf3b5bc7e.yaml b/releasenotes/notes/entity-equivalence-44c0da4cf3b5bc7e.yaml new file mode 100644 index 000000000..9188e7bc4 --- /dev/null +++ b/releasenotes/notes/entity-equivalence-44c0da4cf3b5bc7e.yaml @@ -0,0 +1,8 @@ +--- +features: + - Support definition of entity equivalence. If the equivalence between A and + B is configured, all scenarios linked to entity A will be expanded to + equivalent scenarios, i.e. same conditions and actions with the referenced + entity A replaced by entity B. One use case of equivalence is treating + equivalent alarms from multiple data source as the same, but no need for + duplicating scenario definition in templates.