(Nucleus): Configuration update via IPC doesn't trigger bootstrap script

[kkurczewski]

Describe the bug
As per docs changing component configuration is supposed to trigger bootstrap.

However changing configuration via IPC doesn't trigger bootstrap. This is inconsistent.

Restarting component or whole Greengrass doesn't fix issue. Bootstrap script is not triggered.

To Reproduce

Example recipe would look like this:

bootstrap:
  Setenv:
    HOME_PATH: "{configuration:/HomePath}"
  Script: |
    cd "$HOME_PATH" && ls

Additionally in run/start section there should be script/app that uses AWS SDK to update config value for HomePath.

Expected behavior

Update configuration via IPC should behave consistently like regular remote/local deployment and should trigger bootstrap (if affected).

Actual behavior

Bootstrap script is not triggered which breaks particular component.

Environment

• Nucleus version: latest

Additional context

Basically, I want to create component that is able to restart Greengrass (or machine) on demand (for various reasons). Ideally component should not use privileged user and rely just on on Greengrass access policy (for Restart/Update configuration).

What I considered:

• Restarting component via IPC is not enough because it doesn't trigger Nucleus restart.
• Greengrass CLI is not viable option
  1. it gives shell API whereas I'm interested in programmatic access
  2. it gives too broad privileges (local deployments)
  3. my component is intended for production setup for which Greengrass CLI is not advised

Similar use case:
#1331

[saranyailla]

Hi, the behavior you're seeing with IPC configuration updates is by design. IPC configuration updates are meant for dynamic, runtime changes that components can handle while running, and they don't trigger restarts or bootstrap operations. This is distinct from configuration updates during deployments, which is what the documentation refers to. The documentation could be clearer about the distinction between IPC configuration updates and deployment-based configuration changes.

So, to address the need to restart Greengrass/device through the configuration updates of a component, consider

• Using proper deployment mechanisms (bootstrap) either local or remote, to apply component configuration updates.
• Implementing a separate control mechanism for managed GG/device restarts from within your component.