cloudify-cosmo/Execute Terraform Environment Apply

Execute a terraform apply on already created environment, or create one if it doesn't exist.

Trust Signals

workflow.ymlSHA-pinned

uses: cloudify-cosmo/terraform-apply-action@004955c6c5e3827404856dc8b3e16ac5f5617c75 # v1.3

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
environment-name	Name of Cloudify environment to handle terraform apply	yes	—
environment-id	Id of Cloudify environment to handle terraform apply	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	-

name	description
terraform-outputs	Terraform module outputs