-
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: AWS SAM CLI with Terraform does not read TF_VAR_** environment values for Windows #5670
Comments
Thanks jfuss! As an addition, if I use |
thanks @s-stefanov for raising this issue, I will work on reproducing this issue and see how can we resolve it. |
@moelasmar I manage to have a workaround with a |
sorry @s-stefanov for late reply, I used this sample TF project to test passing the TF variables as environment variable in windows. As you see here Lines 3 to 6 in 5e864e7
The project expects a variable to refer to the Lambda function source code, I executed the following commands on Powershell:
I also get it working on CMD. Could you please share with us your Terraform Project to investigate more. |
Thanks for reporting this. Closing this issue due to inactivity, please create new issue if you come across any more issues. |
|
Description:
Windows specific
Executing
sam build --hook-name terraform --beta-features
Does not reads Terraform Vars using Environment Variables TF_VAR_**
Steps to reproduce:
$Env:TF_VAR_aws_account='some_account'
sam build --hook-name terraform --beta-features
Observed result:
Terraform Plan still asks for input for the variables defined in the TF files
Expected result:
Terraform reads these variables from Environment
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.94.0Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered: