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

Secret outputs for classic vpn not marked sensitive break plan/apply #158

Closed
qbaze opened this issue May 12, 2024 · 1 comment
Closed

Secret outputs for classic vpn not marked sensitive break plan/apply #158

qbaze opened this issue May 12, 2024 · 1 comment
Labels
bug Something isn't working Stale

Comments

@qbaze
Copy link
Contributor

qbaze commented May 12, 2024

TL;DR

As secret outputs in classic vpn are not marked sensitive=true plan and apply are broken

Expected behavior

Secret outputs marked sensitive and plan/apply works.

Observed behavior

Plan/apply doesn't work because sensitive outputs not marked sensitive.

│ 
│   on outputs.tf line 52:
│   52: output "ipsec_secret-static" {
│ 
│ To reduce the risk of accidentally exporting sensitive data that was
│ intended to be only internal, Terraform requires that any root module
│ output containing sensitive data be explicitly marked as sensitive, to
│ confirm your intent.
│ 
│ If you do intend to export this data, annotate the output value as
│ sensitive by adding the following argument:
│     sensitive = true
╵
ERRO[0025] Terraform invocation failed in ```

### Terraform Configuration

```hcl
na

Terraform Version

1.5.7

Additional information

No response

@qbaze qbaze added the bug Something isn't working label May 12, 2024
qbaze added a commit to qbaze/terraform-google-vpn that referenced this issue May 21, 2024
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jul 11, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

1 participant