# How to hide local\_file content during plan?

**URL:** <https://discuss.hashicorp.com/t/how-to-hide-local-file-content-during-plan/27263>\
**Category:** Terraform\
**Created:** [July 25, 2021, 11:46am UTC](https://discuss.hashicorp.com/t/how-to-hide-local-file-content-during-plan/27263 "2021-07-25T11:46:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pobek](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/pobek/32/21022_2.png) [@Pobek](https://discuss.hashicorp.com/u/Pobek)\
**Post date:** [July 25, 2021, 11:46am UTC](https://discuss.hashicorp.com/t/how-to-hide-local-file-content-during-plan/27263/1 "2021-07-25T11:46:40Z")

</div>

Hi there!,

I have a local\_file resource that takes a filename as an input (the file already exists with sensitive content). Whenever I run `terraform plan` or `terraform apply`, The content of the file are shown, no matter where I try and put the keyword `sensitive`.

local\_file example:

```auto
data "local_file" "information" {
  filename = sensitive(local.sensitive_file)
  depends_on = [null_resource.gather_information]
}

```

plan example:

```auto
data "local_file" "information" {
      ~ content = "secret_text_here" -> (known after apply)
      ~ content_base64 = "base_64_secret_text_here" -> (known after apply)
      ~ id = "1abe6c6cf786958bed2d7e03f958a6face819851" -> (known after apply)
        # (1 unchanged attribute hidden)
    }

```

Is there a way to somehow hid or disable the logging of `content` and `content_base64`?

Thanks! 🙂

---

<div class="post-metadata">

**Author:** ![apparentlymart](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/apparentlymart/32/702_2.png) [@apparentlymart](https://discuss.hashicorp.com/u/apparentlymart)\
**Post date:** [July 27, 2021, 1:07am UTC](https://discuss.hashicorp.com/t/how-to-hide-local-file-content-during-plan/27263/2 "2021-07-27T01:07:19Z")

</div>

Hi @Pobek,

There is currently now way to make Terraform treat a resource attribute as sensitive unless the provider itself marks it so. The `local_file` provider doesn’t really know what your file represents and so it doesn’t know to mark it as sensitive, and there’s currently no way to tell it that.