It is possible to limit the scope by using the node_ids and node_instance_ids parameters, specifying lists of
#Terraform plugins docs zip
Terraform_source: Base64 encoded representation of the zip containing the Terraform modules. Is_drifted: True if there are drifts between the template and the actual state, else False.
Installation_source:, format described here. Inputs : terraform_installation_source : description : > In the following example we deploy a Terraform installation: A path on the Conductor Manager to a directory where Terraform plugins are located. The default behavior is to create temporary files.
A path on the Conductor Manager to a directory where the plan files are located. It is your Studio Conductor Administrator’s responsibility to ensure this binary is on the system and that it is executable by the cfyuser. executable_path: Where the Terraform binary is located in the Conductor Manager.plugins: List of plugins to download and install.installation_source: Location to download the Terraform installation from.use_existing_resource: a boolean to indicate if the user want use pre-exising installation of terraform, that will skip the installation, but will download the plugins that is specified in plugins.It should be executable by the cfyuser Linux user. You must already have the Terraform binary on your Conductor Manager. The Terraform plugin enables you to maintain Terraform Plan state from Studio Conductor and also to use Terraform resources in your Studio Conductor blueprints. Kubernetes Plugin Utilities Plugin Page Contents