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

data.vault_generic_secret: make data and data_json sensitive #844

Merged
merged 1 commit into from
Aug 20, 2020
Merged

data.vault_generic_secret: make data and data_json sensitive #844

merged 1 commit into from
Aug 20, 2020

Conversation

stellirin
Copy link
Contributor

Changes to Terraform 0.13.0 mean that these values are currently
printed during terraform apply.

See hashicorp/terraform#25800 for discussion.

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Release note for CHANGELOG:


Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

Changes to Terraform 0.13.0 mean that these values are currently
printed during terraform apply.

See hashicorp/terraform#25800 for dicussion.
@ghost ghost added the size/XS label Aug 11, 2020
@m0ps
Copy link

m0ps commented Aug 12, 2020

This is an urgent change... With terraform v 0.13 all secrets become exposed in the plan output

@yatanasov
Copy link

Hello, when can we expect a fix/next release for this ? Thank you!

@ajinkyakadam
Copy link

Our team is facing the same issue, with sensitive data shown in plan output. Is there an ETA for a fix ? Thanks.

Copy link
Contributor

@catsby catsby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks!

@catsby catsby merged commit 19f4e27 into hashicorp:master Aug 20, 2020
@catsby
Copy link
Contributor

catsby commented Aug 20, 2020

Hello - we'd like to roll this fix out as soon as possible, however I'm investigating #847 as well and feel that should be included.

@catsby
Copy link
Contributor

catsby commented Aug 28, 2020

Hello all - this was released in v2.13.0 , thanks for the contribution and your patience!

@jravetch
Copy link

Hi @catsby We are on 2.14 with tf 0.13.3 and we are seeing some regression of #849 whereby the data.vault_generic_secret is read every plan and requires a new plan/apply.

# data.vault_generic_secret.gcp_oauth_token will be read during apply
  # (config refers to values not yet known)
 <= data "vault_generic_secret" "gcp_oauth_token"  {
      ~ data             = (sensitive value)
      ~ data_json        = (sensitive value)
        id               = "gcp/token/xxx"
        lease_duration   = 0
        lease_renewable  = false
        lease_start_time = "RFC5559"
        path             = "gcp/token/xxx"
        version          = -1
    }

Is it possibly related to #844 ? Thanks!

@catsby
Copy link
Contributor

catsby commented Sep 30, 2020

Hey @jravetch - could you open a separate issue with an example configuration that reproduces this?

dandandy pushed a commit to dandandy/terraform-provider-vault that referenced this pull request Jun 17, 2021
…rp#844)

Changes to Terraform 0.13.0 mean that these values are currently
printed during terraform apply.

See hashicorp/terraform#25800 for dicussion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants