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

Support for configuring http backend using environment variables #22527

Closed
jbloxsome opened this issue Aug 20, 2019 · 3 comments
Closed

Support for configuring http backend using environment variables #22527

jbloxsome opened this issue Aug 20, 2019 · 3 comments

Comments

@jbloxsome
Copy link

Current Terraform Version

Terraform v0.12.3

Your version of Terraform is out of date! The latest version
is 0.12.6. You can update by downloading from www.terraform.io/downloads.html

Use-cases

Currently, when using an http remote backend, users must configure access details in code i.e

terraform {
  backend "http" {
    address = "http://myrest.api.com/foo"
    lock_address = "http://myrest.api.com/foo"
    unlock_address = "http://myrest.api.com/foo"
    username = "user"
    password = "secret"
  }
}

Support for environment variable configuration would allow users to remove sensitive information
such as passwords from the HCL code.

Proposal

Add support for configuring access to an http remote backend using environment variables e.g.

HTTP_BACKEND_URL
HTTP_BACKEND_USERNAME
HTTP_BACKEND_PASSWORD

@nicholasklick
Copy link

@pkolyvas This can be closed I assume since it was resolved by #25439

@pkolyvas
Copy link
Contributor

pkolyvas commented Sep 3, 2020

Thanks @nicholasklick !

@pkolyvas pkolyvas closed this as completed Sep 3, 2020
@ghost
Copy link

ghost commented Oct 13, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked as resolved and limited conversation to collaborators Oct 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants