Using componentName in UpdateConfigurationRequest

[AntonBy]

I wanted to update other component configurations (e.g. the MqttBridge ) dynamically from my custom component. However, I couldn't find a way to do it, except through cloud-deployments / subdeployments.

I noticed that SubscribeToConfigurationUpdateRequest has an optional componentName property.

Is it possible to add a similar property to the UpdateConfigurationRequest ?

Nucleus implementation for SubscribeToConfigurationUpdateRequest handler

Nucleus implementation for UpdateConfigurationRequest handler

[bretambrose]

This question is best asked on the greengrass nucleus repository. Our insight into nucleus behavior is probably the same as yours.

[MikeDombo]

A component may only update its own configuration, it cannot update another component's configuration.

To update other components, you must use a deployment. You can create a deployment in your component using the API: https://docs.aws.amazon.com/greengrass/v2/developerguide/ipc-local-deployments-components.html#ipc-operation-createlocaldeployment

[AntonBy]

Thanks for super quick response.

1. "To update other components, you must use a deployment." - does it mean there is a technical limitation/complexity to add this functionality or you just describe the current situation? I'm trying to understand whether I create a feature request for this functionality( or not) in Nucleus repository.

2. Now I'm using complex deployment approach: Group deployements for fleet(delivery components), Subdeployments for each "updateConfigurationForDevice" operation. I'm not sure it's the best approach and wanted to try to use IPC client to update configuration. You mentioned that I can use LocalDeployments to do it, but it looks pretty similar to Subdeployments. I would like to understand the differences between LocalDeployments, Subdeployments and Deployments. Is there any comparison table?

PS: I saw your post https://dev.to/iotbuilders/managing-per-device-configuration-with-an-aws-iot-greengrass-fleet-4obk but as I understood, I can't use ConfigHolder approach in my case(MQTT Bridge configuration update).

[MikeDombo]

It was a security limitation, but now the auth model could support this request. You should make a feature request in the Nucleus repo.

[AntonBy]

Added the feature request to Nuclues repository aws-greengrass/aws-greengrass-nucleus#1712