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

질문됨 한 달 전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

답변함 한 달 전

전문가

Greg_B

검토됨 한 달 전

bruce
한 달 전
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 전문가
한 달 전
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?

관련 콘텐츠