| commit | 25c8a555a739b1c80966ed88cc123a6e9ad9318e | [log] [tgz] |
|---|---|---|
| author | Jim Hahn <jrh3@att.com> | Mon Aug 31 17:59:44 2020 -0400 |
| committer | Jim Hahn <jrh3@att.com> | Mon Aug 31 18:04:27 2020 -0400 |
| tree | d165abf12e68cf51219bcb2f3ff128cdf36a0570 | |
| parent | 1c5cb8a0d740ccd92d2b3fdce8eb192cd20b147f [diff] |
Allow guards to be dynamically enabled/disabled Modified drools-apps so that guards can be dynamically enabled and disabled. Due to the current design, there are two properties that control this: - an actor-level property: when enabled, the DB connection is created, otherwise a stub connection is created. This property is NOT dynamic - an engine-level property: when enabled, the connection created by the actor is used, otherwise a stub connection is used. This property IS dynamic Issue-ID: POLICY-2748 Change-Id: I2a5baf908ce274f2eb46a6a3f01df1b3532038ff Signed-off-by: Jim Hahn <jrh3@att.com>
Copyright 2018-2020 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
This source repository contains ONAP Policy application code. To build it: