Greengrass v2 | Component Configuration Cached on Device

0

I created a new version of a custom Greengrass component and deployed it to my GG core device, which was running the previous version of my custom component.
After the deployment is complete, I noticed that the new component's configuration remained the same as the old component, even though the default configuration has changed in this new version of component. This caused Unauthorized Error since the new access control policies did not get updated.
Was the component configuration cached by the Nucleus? How can I make sure my updates to my custom component updates both the artifact, recipe, and the configuration?

ictwist
質問済み 1年前365ビュー
1回答
1
承認された回答

Use "reset": [""] to reset all configuration to the default value in the recipe. See https://docs.aws.amazon.com/greengrass/v2/developerguide/update-component-configurations.html#reset-configuration-update for more.

Cheers,

Michael

AWS
エキスパート
回答済み 1年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ