1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
2
Hello,
To answer the questions:
- Yes, your assumption is correct. When a deployment is made to a thing group, the configuration and the component versions are uniform across all the things which are a part of the thing group. The configuration for the component can however be overridden on a per device basis using a separate component for configuration.
- You can also use a static file per device, managed separately on your end which can be used by the code running on the component to get the custom parameters for the specific device. You can also facilitate this using a custom component to get the device ID and download the configuration for the specific device ID from a remote location (like an S3 bucket or your FTP server). Using this custom component as a part of the group deployment will allow you to have a single deployment to get the custom settings for running your code tuned to the specific device. Downloading the static files based on the device ID via your code allows you more customisation on downloading the configuration file for your code.
Hope this helps.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
Thanks. So to summarize, in any case, we will have to implement something that will have to handle configuration specifics for a Thing, including the changes in configuration.
In this case, we will use device shadows rather than other implementations based on S3 buckets, static files and a dedicated configuration component for the following reasons :
Thanks again for the clarifications!