Closed AlvaroVega closed 1 year ago
Maybe we should tell in someplace in the documentation how this works. I mean, something like this:
In the case of autoprovisioned devices, the associated document created in database doesn't include config group parameters (timestamp and explicitAttrs in particular). That way, these parameters can freely established modifying the device information after creation using the provisioning API. However, note that if a device (autoprovisioned or not) doesn't have these parameters defined at device level in database, the parameters are inherit from config group parameters.
Not sure where to include such fragment. Do we have some place in which autoprovisioned devices are explained? @mapedraza what do you think?
Maybe we should tell in someplace in the documentation how this works. I mean, something like this:
In the case of autoprovisioned devices, the associated document created in database doesn't include config group parameters (timestamp and explicitAttrs in particular). That way, these parameters can freely established modifying the device information after creation using the provisioning API. However, note that if a device (autoprovisioned or not) doesn't have these parameters defined at device level in database, the parameters are inherit from config group parameters.
Not sure where to include such fragment. Do we have some place in which autoprovisioned devices are explained? @mapedraza what do you think?
I agree, it seems reasonable. Maybe a new chapter explaining autoprovision under https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/api.md#iot-agent-information-model
Maybe we should tell in someplace in the documentation how this works. I mean, something like this:
In the case of autoprovisioned devices, the associated document created in database doesn't include config group parameters (timestamp and explicitAttrs in particular). That way, these parameters can freely established modifying the device information after creation using the provisioning API. However, note that if a device (autoprovisioned or not) doesn't have these parameters defined at device level in database, the parameters are inherit from config group parameters.
Not sure where to include such fragment. Do we have some place in which autoprovisioned devices are explained? @mapedraza what do you think?
I agree, it seems reasonable. Maybe a new chapter explaining autoprovision under https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/api.md#iot-agent-information-model
Could you add such documentation to PR https://github.com/telefonicaid/iotagent-node-lib/pull/1391, pls?
Could you add such documentation to PR telefonicaid/iotagent-node-lib#1391, pls?
Yes, I opened an issue but I will add to that PR
Could you add such documentation to PR telefonicaid/iotagent-node-lib#1391, pls?
Yes, I opened an issue but I will add to that PR
Taking into account the modification to the documentation is mall, I'd suggest in the PR we have now on the table (ideally, we should should include code + test + doc in the same PR, only when this cannot be done we use "debt" issues).
I have found another section that can be relevant: https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/api.md#autoprovision-configuration-autoprovision
Could you add such documentation to PR telefonicaid/iotagent-node-lib#1391, pls?
Yes, I opened an issue but I will add to that PR
Taking into account the modification to the documentation is mall, I'd suggest in the PR we have now on the table (ideally, we should should include code + test + doc in the same PR, only when this cannot be done we use "debt" issues).
I have found another section that can be relevant: https://github.com/telefonicaid/iotagent-node-lib/blob/master/doc/api.md#autoprovision-configuration-autoprovision
related https://github.com/telefonicaid/iotagent-node-lib/pull/1391