This version bump brings following improvement requested via PCF-1666:
Get requests that contain paths spanning multiple USP Services (eg Device.) result in a get
request to each USP Service containing a list of all fully resolved parameters. It is more
efficient to perform a get of the top level DM element(s) registered by each USP Service.
Then apply max_depth and read permissions to the parameters returned, before combining into
a final Get Response to the original Get Request.
Additionally this bump to obuspa version 9.0.7 brings following changes
since version 9.0.3:
* obuspa version 9.0.7
Added:
* HardwareVersion can also be specified by an environment variable
(USP_BOARD_HW_VERSION)
Fixed:
* Crash that could occur once at startup if the controller trust
permissions table contained invalid data
* obuspa version 9.0.6
Added:
* Example vendor layer plug-in and documentation (in quick start guide)
* obuspa version 9.0.5
Fixed:
* Compilation failure when building for pure USP Service
* Subscription ID should be immutable
* OpenSSL should be initialized only once
* obuspa version 9.0.4
Added:
* USP Broker support for registration of parameters, events and USP
commands (USP 1.4)
* Bulk Data Collection over MQTT
Fixed:
* Event and OperationComplete subscriptions to 'Device.' on a USP
Broker now set subscriptions on each USP Service containing only
the DM elements that were registered (PCF-1666)
* USP Conformance test 11.11 failure: MQTT PUBLISH frames should not
be sent until SUBACK frame indicates successfully subscribed
Since the obuspa version 9.0.4 brought a new Bulk Data Collection over
MQTT feature, the obuspa.t cram test was updated with expected new
datamodel Device.BulkData.Profile.{i}.MQTT. addition.
Closes: PCF-1666
Signed-off-by: Steven Corby <steven.corby@vantiva.com>
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> [commit facelift, test update]
9de5dc5636