Different GreenGrass v2 component configurations depending on tevice tag

Question

Is there a way to deploy a component with different configuration for each device group or tag ? We have different kind of device that should have slightly different component behavior. For instance, a device A may not want to use sensor X. Is there a way to have a deployment that deploys to all my devices, but has a configuration parameter specifically for device A ?

I could implement htat using an API call ListTagsForResource but that would happen too late in my workflow.
I could also have two different deployments with different config, but then I have no guarantee that all my device are running the same component version, plus the logic would now be replicated in two deployments.

Edit: There seems to be a way to achieve it by setting "platformOverride" to the nucleus component, altough I am not sure how that would be done

Accepted Answer

Hi again TSpark,

I'd suggest that you create a component to hold the device-unique configurations you need. Let's call it simply "Config". You will create a deployment for each device that needs its own values and you will deploy only "Config". In the deployment, you will merge in the device-specific values.

Components in the group deployment which need device-specific information can use our [GetConfiguration](https://docs.aws.amazon.com/greengrass/v2/developerguide/ipc-component-configuration.html#ipc-operation-getconfiguration) API in order to read the configuration. If you do not want to use IPC, then the configuration can also be interpolated into the component's lifecycle such as `{Config:configuration:/configPath}`, where "Config" is your config component name.

As another simple option if the configuration is going to be static, then of course you could simply have a file on the device that contains whatever unique information it needs.

Different GreenGrass v2 component configurations depending on tevice tag

Relevant content