-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task/allow devices same device id in same path but apikey #1592
Task/allow devices same device id in same path but apikey #1592
Conversation
has been provisioned with `type=X`/`apiKey=111` and no other config group has been provisioned. | ||
are identified by a `device_id`, and they are associated to an existing config group based in `apiKey` matching. For | ||
instance, let's consider a situation in which a config group has been provisioned with `type=X`/`apiKey=111` and no | ||
other config group has been provisioned. | ||
|
||
The IoT Agents offer a provisioning API where devices can be preregistered, so all the information about service and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make this more explicit, maybe we can add a new sub-section after ### Devices
with the following text:
Uniqueness of groups and devices
- Group service uniqueness is defined by the combination of: service, subservice and apiKey
- Device uniqueness is defined by the combination of: service, subservice, device_id and apiKey. Note that the several devices with the same device_id are allowed in the same service and subservice as long as their apiKeys are different.
Please, check, just in case I can be wrong with the above text...
(Btw, it's a bit weird that device_id uses snake_case but apiKey uses camelCase. In the database the MongoDB fields use the same?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 2b802b2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#1589
Related with #1426 #1435) (#1430)