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

Feature Request: sensitive content #46

Open
manfredlift opened this issue May 31, 2019 · 4 comments · May be fixed by #81
Open

Feature Request: sensitive content #46

manfredlift opened this issue May 31, 2019 · 4 comments · May be fixed by #81

Comments

@manfredlift
Copy link

manfredlift commented May 31, 2019

Provide a way to pass sensitive content to archive_file. At the moment there is no other way to mask a variable or flag an input as sensitive than at the provider level (hashicorp/terraform#16643 (comment)).

Example use case is a rendered template_file with secrets injected into it that we would like to zip.

Three different ways this could be implemented:

data "archive_file" "foobar" {
  type        = "zip"
  output_path = "${path.module}/foobar.zip"

  source {
    content  = "${local.secret}"
    filename = "bar"
    sensitive = true
  }
}
data "archive_file" "foobar" {
  type        = "zip"
  output_path = "${path.module}/foobar.zip"

  source {
    sensitive_content = "${local.secret}"
    filename          = "bar"
  }
}
data "archive_file" "foobar" {
  type        = "zip"
  output_path = "${path.module}/foobar.zip"

  sensitive_source {
    content  = "${local.secret}"
    filename = "bar"
  }
}
@pms1969
Copy link

pms1969 commented Jun 17, 2020

Any progress on this?

@AndrewNeudegg
Copy link

We need this to obscure secrets.

@pms1969
Copy link

pms1969 commented Sep 25, 2020

Nudge

@lwoerdeman lwoerdeman linked a pull request Jan 28, 2021 that will close this issue
@R0flcopt3r
Copy link

We need this to hide some secrets from our tfstate.

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

Successfully merging a pull request may close this issue.

4 participants