actions-marketplace-validations/Terraform Apply for kubernetes cluster in AWS using Vault secrets - works on changes in a PR
This action will perform kubernetes cluster deployment in AWS account using Terraform using secrets in Hashicorp Vault.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Feb 10, 2023
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/paresh-deshmukh_terraform-apply-for-aws-using-secrets-in-vault@54900625a9b1bf1e62f9c130fc1f122a32079ba9 # no releases — HEAD as of 2026-07-10tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| tf-working-dir | Terraform working directory | yes | — |
| terraform-version | Terraform version | yes | — |
| cluster-name | Name of the kubernetes cluster | yes | — |
| aws-role-to-assume | Role ARN in AWS with which the connection to AWS will be established | yes | — |
| aws-region | AWS region | yes | — |
| vault-github-token | GitHub Token used for accessing Vault | yes | — |
| github-token | Pass secret GITHUB_TOKEN | yes | — |
| private-ssh-key | ssh key to clone the terraform modules from the remote repo | yes | — |
| pr-dir | full path of a directory in a PR to filter for the terraform apply | no | — |
| tf-plan-output-filename | Name of the output file for terraform plan command | yes | — |
| apply-terraform | Pass true/false to apply the terraform changes with provided tf-plan-output-filename | no | false |
Outputs
| name | description |
|---|---|
| tf-fmt-outcome | Outcome of the 'terraform fmt' command |
| tf-init-outcome | Outcome of the 'terraform init' command |
| tf-plan-output | Output of the 'terraform plan' command |
| tf-plan-outcome | Outcome of the 'terraform plan' command either success or failure |