Age | Commit message (Collapse) | Author | Files | Lines |
|
*** This commit is generated by a PF release script ***
policy/drools-pdp is update from 1.10.0-SNAPSHOT to 1.10.1-SNAPSHOT
Issue-ID: POLICY-3827
Signed-off-by: liamfallon <liam.fallon@est.tech>
Change-Id: Id6f59849b88c0f98d874cf853f249738e784316f
|
|
Issue-ID: POLICY-3696
Change-Id: Id7723b73aa472c45271e6e1488cc3f0f08349924
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-3696
Change-Id: I8fc7e6a7c6e9a2f20409a84a1c517e49c9468eb8
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-3587
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I6d38adccfbee1274ce416cfadbfe306343f5d607
|
|
This feature makes the legacy configuration optional.
It was used by brmsgw and other tooling to provision
via its DMaaP channel. The capability to configure
via PdpConfiguration object is kept in the core
preserving backwards compatibility, but the DMaaP
provisioning channel(s) are optional.
Issue-ID: POLICY-2618
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: Ia7198ac3b2810d85133c06ba5217a9c28e07ac4c
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
|