[Hawkular-commits] [hawkular/hawkular-alerts] 853f26: A few possible additions to Wintermute

Branch: refs/heads/winter/uuid Home: https://github.com/hawkular/hawkular-alerts Commit: 853f26351af9a9cedf751f831f8d20d0446d957a https://github.com/hawkular/hawkular-alerts/commit/853f26351af9a9cedf751f... Author: Jay Shaughnessy <jshaughn(a)redhat.com&gt; Date: 2015-03-06 (Fri, 06 Mar 2015) Changed paths: M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/CompareCondition.java M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/Condition.java M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/trigger/Trigger.java M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsService.java M hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/DbDefinitionsServiceImpl.java M hawkular-alerts-engine/src/test/java/org/hawkular/alerts/engine/DbDefinitionsServiceImplTest.java Log Message: ----------- A few possible additions to Wintermute - provide a default UUID triggerId if a triggerId is not provided. In most prod cases it seems a generated ID will be desirable. users/apps will likely not be able to provide a unique ID on their own. - pull getDataId() down into the Condition base class as it is common to almost all conditions and makes coding easier. - Add a copyTrigger to the definitions service. This is experimental, the idea being to enable using a Tokenized Trigger and generating a bunch of explicit triggers by provising a map of token dataIds to real dataids.