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?

相關內容