cloudify-cosmo/Execute Terraform Environment Plan
Execute a terraform plan on already created environment, or create one if it doesn't exist.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Oct 5, 2022
- License
- None
Pinned Snippet
uses: cloudify-cosmo/terraform-plan-action@5d11c5f3c2e7705a920a236d6adfdf92175b9b05 # v1.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| environment-name | Name of Cloudify environment to handle terraform plan | yes | — |
| environment-id | Id of Cloudify environment to handle terraform plan | no | - |
| labels | A labels list of the form <key>:<value>,<key>:<value>. Any comma and colon in <value> must be escaped with \. The labels’ keys are saved in lowercase. | no | - |
| module-file | URL/path to Terraform module archive | yes | — |
| module-source-path | path to Terraform module inside the archive | yes | — |
| variables-file | YAML/JSON file containing template variables | no | - |
| environment-file | YAML/JSON file containing environment variables to pass to the Terraform process | no | - |
| environment-mapping | A whitespace-delimited list of strings. For each item: * If it is of the form `k=v`, then the value of the environment variable `k` is passed as environment variable `v` to Terraform * Otherwise, let the value be `x`; then the environment variable `x` is passed as-is to Terraform This effectively passes environment variables, visible to the CI/CD platform, as environment variables to Terraform. Useful, among others, for passing Cloud credentials - stored in the CI/CD platform - to Terraform | no | - |
Outputs
| name | description |
|---|---|
| terraform-plan | Terraform module plan |