Skip to content
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

Enable matching of uppercase environment variables #22671

Open
marpada opened this issue Sep 3, 2019 · 6 comments
Open

Enable matching of uppercase environment variables #22671

marpada opened this issue Sep 3, 2019 · 6 comments

Comments

@marpada
Copy link

marpada commented Sep 3, 2019

Current Terraform Version

Terraform v0.12.7

Use-cases

The documentation about TF_VAR env variables says

On operating systems where environment variable names are case-sensitive, Terraform matches the variable name exactly as given in configuration, and so the required environment variable name will usually have a mix of upper and lower case letters as in the above example.

Our CD/CI managed system (Azure Pipelines) agent can run on Linux instances, but the agent converts environment variables to uppercase. microsoft/azure-pipelines-agent#1645
To workaround this issue it would be good if Terraform could be configured to match uppercase environment variables.

Proposal

Introduce a command line flag allow matching of uppercase environment variables.

References

microsoft/azure-pipelines-agent#1645

@tobiasbueschel
Copy link

This would also be great to have for GitHub Action repository environment variables as GitHub automatically converts to uppercase!

@orefalo
Copy link

orefalo commented Jun 3, 2022

same issue here

@guidooliveira
Copy link

same issue

2 similar comments
@mijhael3000
Copy link

same issue

@ivancorroto
Copy link

same issue

@crw
Copy link
Collaborator

crw commented Mar 17, 2023

Thanks for your interest in this issue! This is just a reminder to please avoid "+1" comments ("same issue"), and to use the upvote mechanism (click or add the 👍 emoji to the original post) to indicate your support for this issue. Thanks again for the feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants