In IoT Server v3.1.0 geo location services is enabled with the following configuration; GeoLocationConfiguration -> isEnabled -> true and GeoLocationConfiguration -> PublishLocationOperationResponse -> true. With the new feature developments; In latest IoT Server(master branch); now we also allow publishing device-info responses through the same configuration. OperationAnalyticsConfiguration -> isEnabled -> true and OperationAnalyticsConfiguration -> PublishOperationResponse -> true. However; there might be use cases for enabling geo location services without publishing all the device-info into IoT-Analytics server. Also; it should allow publishing any device response to the IoT Analytics server.
This PR resolves https://github.com/wso2/product-iots/issues/1611.
Goals
This PR will introduce configuration changes for enabling geo location services. Introduced a separate configuration for publishing the location response and device-info responses into IoT Analytics Server.
Approach
Following configuration is introduced;
<GeoLocationConfiguration>
<isEnabled>false</isEnabled>
</GeoLocationConfiguration>
<OperationAnalyticsConfiguration>
<PublishLocationResponse>false</PublishLocationResponse>
<PublishDeviceInfoResponse>false</PublishDeviceInfoResponse>
<PublishOperationResponse>
<isEnabled>false</isEnabled>
<operations>
<!-- Publish specific operation responses -->
<!--
<operation>BATTERY_LEVEL</operation>
<operation>CHECK_LOCK_STATUS</operation>
-->
<!-- use wildcard '*' to publish all responses -->
<operation>*</operation>
</operations>
</PublishOperationResponse>
</OperationAnalyticsConfiguration>
Purpose
Goals
Approach
User stories
Release note
Documentation
Training
Certification
Marketing
Automation tests
Security checks
Samples
Related PRs
Migrations (if applicable)
Test environment
Learning