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

fix: added sensitive flag to the api_key output #67

Merged
merged 1 commit into from
Apr 12, 2024

Conversation

vikas027
Copy link
Contributor

@vikas027 vikas027 commented Apr 11, 2024

Hello @shibayan ,

Terraform was throwing the below error related to the sensitive value of api_key. I have just added sensitive = true in the api_key output.

Here is the output of the terraform

2024-04-11_20-16-49

Terraform was throwing below error related to sensitive
value of api_key

---
│ Error: Output refers to sensitive values
│
│   on outputs.tf line 16:
│   16: output "api_key" {
│
│ 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
---
Copy link
Owner

@shibayan shibayan left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

@shibayan shibayan merged commit 2a7a824 into shibayan:master Apr 12, 2024
2 checks passed
@vikas027
Copy link
Contributor Author

Thanks for quickly merging the PR @shibayan .
Can you please release a new version (3.0.3) too? Thanks in advance.

@vikas027 vikas027 deleted the fix_sensitive_output branch April 14, 2024 02:59
@shibayan
Copy link
Owner

We have just released v3.0.3. Thanks for your contribution.

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 this pull request may close these issues.

2 participants