使用AWS re:Post即您表示您同意 AWS re:Post 使用条款

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?

已提问 2 年前531 查看次数
1 回答
2
已接受的回答

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
专家
已回答 2 年前
profile picture
专家
已审核 6 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则