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(docs): Fix typo in example of using TF_VAR_ to set TerraformVariable #3116

Merged
merged 1 commit into from
Sep 1, 2023

Conversation

ameerkat
Copy link
Contributor

Minor: Changing TF_VAR_adminPasword to TF_VAR_adminPassword to match the text in the block above and resolve typo.

Related issue

Fixes: NA

Description

Noticed a typo in the Read Secrets with Terraform Variables on https://developer.hashicorp.com/terraform/cdktf/create-and-deploy/best-practices#read-secrets-with-terraform-variables

In particular the example code says TF_VAR_adminPasword='<your password>' and missing the second s in password, which is correctly spelled in the preceding code block.

Checklist

This is a one character change to documentation. If you feel the need to run the checklist please let me know.

@ameerkat ameerkat requested review from a team as code owners August 31, 2023 16:23
@ameerkat ameerkat requested review from mutahhir and DanielMSchmidt and removed request for a team August 31, 2023 16:23
@hashicorp-cla
Copy link

hashicorp-cla commented Aug 31, 2023

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@ansgarm ansgarm left a comment

Choose a reason for hiding this comment

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

Thank you, @ameerkat 💯

Changing TF_VAR_adminPasword to TF_VAR_adminPassword to match the text in the block above and resolve typo.
@ansgarm ansgarm changed the title chore: Fix typo in example of using TF_VAR_ to set TerraformVariable fix(docs): Fix typo in example of using TF_VAR_ to set TerraformVariable Sep 1, 2023
@DanielMSchmidt DanielMSchmidt merged commit a66ca59 into hashicorp:main Sep 1, 2023
31 of 32 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants