Are there any excluded environment variables in Greengrass component recipes?

I'm trying to set up environment variables in a Greengrass component recipe. My Setenv section looks like:

 "Setenv": {
      "PYTHONPATH": "{artifacts:decompressedPath}",
      "GG_ROOT_PATH": "{kernel:rootPath}",
       ... more env vars
}

GG_ROOT_PATH and my other env vars get set correctly, but PYTHONPATH doesn't, no matter where I place it in the list of variables.

Is there some internal restriction using some names for environment variables?

主题

物联网 (IoT)

标签

AWS IoT Greengrass

语言

English

bruce

已提问 1 个月前106 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

已接受的回答

Hi,

This is done by sudo on your system. You can configure sudo to stop resetting environment, or you can set the environment on the command line directly as such: PYTHONPATH=<my path> python3 <rest of your command here>

Cheers,

Michael

专家

MichaelDombrowski-AWS

已回答 1 个月前

专家

Greg_B

已审核 1 个月前

bruce
1 个月前
Okay thanks for the info - makes sense now that I've looked up how sudo behaves for environment variables. But that seems like a bug in how Greengrass uses sudo then - I ask for it to set a specific environment variable and it just goes poof. So if I ever wanted to override an existing environment variable using Setenv I can't do it, and that's not mentioned anywhere in the docs.
MichaelDombrowski-AWS 专家
1 个月前
Thank you for the feedback, unfortunately we are not able to change the way that sudo behaves however we can certainly document this behavior.

Are there any excluded environment variables in Greengrass component recipes?

相关内容