fix support for device configuration groups (#102) #103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tion#102) This commit provide support for inheriting dynamically the configuration of a group for a device belonging to the group * when a message is received, we search for its device group * the device configuraiton is the merge of the device group and device configuration * if a device does not exist when a message arrives, the self registration creates a device with empty configuration (in this way any change to the device group configuration will be carried over also to devices already self provisioned)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit provide support for inheriting dynamically the configuration of a group for a device belonging to the group (#102)
other fixes are introduced, for example, self provisioned devices are now mapped to
type:deviceIdentityId (following standard data model naming) rather thandeviceId:type