Components with a lifecycle step that varies depending on recipe variable substitution will not be restarted if the recipe variable changes

[rawalexe]

In Greengrass classic, components will be restarted if the “run” lifecycle phase changes after a deployment. This may include run lifecycle phases that use variable interpolation to include something from the component configuration in the lifecycle script. Greengrass Lite will not detect that a component lifecycle phase has changed in the event of a configuration change changing the recipe variable used in the lifecycle script, so these components will not restart if the version has not changed.

Workaround: Components should use the SubscribeToConfigurationUpdate IPC command to subscribe to configuration changes and update their process to use new values. If this is not possible, an easier workaround may be to simply bump the component version in order to force a component restart.