-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: sam sync does not have --container-env-var-file parameter #6427
Comments
Hi, thanks for bringing up the issue. It looks like we only support --container-env-file option on |
any updates on this? |
@jysheng123 i would like to work on this. But, I'm facing one issue while writing unit tests for same. |
Hi @nitintecg, if you are interested to contribute feel free to open a PR and our team would be happy to review and assist with unit tests. I don't recall if we have specific guidelines on writing unit tests, but you can follow the existing unit tests to get some idea. |
Closing as the PR has been merged and released. |
|
Description:
It appears that sam sync doesn't support passing in of
--container-env-var-file
when using the--use-container
flag.This means that when building the code it's missing any environment variables needed to compile the project.
Steps to reproduce:
Run
sam sync --use-container --container-env-var-file container.env.json
. Variable files are not respected as persam build
or other commands.Observed result:
Container builds that require env vars have those vars unset.
Expected result:
Environment variables are passed into container as per
sam build
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
The text was updated successfully, but these errors were encountered: