4.6.0 policy-handler - active-passive

DCAEGEN2-931:
- exposed POST /reconfigure endpoint on the web-server
  that initiates the reconfigure process right away

DCAEGEN2-932:
- mode_of_operation: active or passive
  = active is as before this change
  = in passive mode the policy-handler
    * closes the web-socket to PDP
    * skips the periodic catch_ups
    * still periodically checks for reconfigure
    * still allows usig the web-server to retrieve policies from PDP
- default is active

- when mode_of_operation changes from passive to active,
  the policy-handler invokes the catch_up right away

- config-kv contains the optional override field mode_of_operation
  = changing the mode_of_operation in config-kv and invoking
    POST /reconfigure will bring the new value and change the
    mode of operation of the policy-handler if no service_activator
    section is provided in consul-kv record

- if config-kv contains the service_activator section,
  = the policy-handler registers with service_activator - untested
  = and receives the mode_of_operation - untested
  = service_activator can POST-notify the policy-handler to
    initiate the /reconfigure

- reduced the default web-socket ping interval from 180 to 30
  seconds because PDP changed its default timeout on the web-socket
  from 400 seconds to 50 seconds

Change-Id: If7dd21c008d9906aca97939be65dfa9c2f007535
Signed-off-by: Alex Shatov <alexs@att.com>
Issue-ID: DCAEGEN2-931
Issue-ID: DCAEGEN2-932

1 files changed, 1 insertions, 1 deletions

diff --git a/version.properties b/version.properties
index aae9468..314217b 100644
--- a/version.properties
+++ b/version.properties
@@ -1,5 +1,5 @@
 major=4

-minor=5

+minor=6

 patch=0

 base_version=${major}.${minor}.${patch}

 release_version=${base_version}