The ID of the credentials to use when accessing Azure. Parameters' expansion is supported when using freestyle jobs.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

If checked, then the created environment's data will be printed to the job's log.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

Path to a file that will contain the created environment's data. If not provided, the environment data won't be written.

The Azure location where the created resource group should reside in. If omitted, the value of the azure_default_location Cloudify secret will be used.

YAML/JSON of parameters to pass to the template.

Path, relative to the Jenkins workspace root, of a YAML/JSON file containing parmaeters to pass to the template.

Name of resource group to create for the template.

Workspace-relative path of the ARM template file.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

The ID of the credentials to use when accessing AWS. Parameters' expansion is supported when using freestyle jobs.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

ID to assign to the created Cloudify deployment. If not provided, one will be randomly generated. You can obtain the deployment ID from the "environment data" output file.

If checked, then the created environment's data will be printed to the job's log.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

Path to a file that will contain the created environment's data. If not provided, the environment data won't be written.

Path, relative to the Jenkins workspace root, of a YAML/JSON file containing parmaeters to pass to the template.

AWS region to use. If not specified, the value of the aws_region_name secret is used.

Name of the new stack.

URL of the Terraform template. May be a ZIP, tar.gz, or a Git repository.

Unique identifier for the created deployment.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

Identifies the blueprint to create a deployment off.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

At the end of the build step, print the outputs and capabilities to the console.

A YAML/JSON containing inputs for the deployment. These inputs will be merged with inputs provided through the " inputs file " parameter.

A path (relative to the workspace root) to a YAML/JSON file containing inputs for the deployment. These inputs will be merged with inputs provided through the " inputs " parameter.

If specified, this YAML/JSON will be used to transform a YAML/JSON coming from the "inputs file" parameter. This is useful if the "inputs file" is the result of a different Cloudify environment build.

This parameter must not be provided if "mapping file" is provided.

If specified, this YAML/JSON file will be used to transform a YAML/JSON coming from the "inputs file" parameter. This is useful if the "inputs file" is the result of a different Cloudify environment build.

This parameter must not be provided if "mapping" is provided.

Name of file into which the deployment's outputs and capabilities will be written. The file will be a JSON, adhering to the following format:

{
    "outputs": <outputs_dictionary>,
    "capabilities": <capabilities_dictionary>
}
	

Only create a Cloudify deployment; skip running the install workflow.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

ID of blueprint to delete.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

If checked, and this is the last environment for the associated blueprint, then also delete the blueprint.

If checked, then failures during the removal of the environment will be ignored.

Only delete the Cloudify deployment; skip running the uninstall workflow.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

ID of the Cloudify environment to delete.

Parameters to pass to the execution, in YAML/JSON format.

If checked, then the execution's events and logs are printed to the build log. Note that this implies "wait for completion".

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

If checked, then the build waits for the execution to finish. If the execution ends in any way other than success, the build step will fail.

The ID of the workflow to execute.

The ID of the credentials entry that contains the API key.

This parameter is optional; the API key may also be provided through "API options", however this method is preferred.

If provided, then this credentials entry must either be of type "text" or "file". In the latter case, the file is read as-is and the resultant string is used as the API credentials.

Path to file, relative to the Jenkins workspace, containing the API key.

This parameter is optional, as the API key may be provided by other means.

Path, relative to the workspace's root, of a file containing the CA certificates store to use for verifying the Kubernetes host's certificate.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

The Kubernetes application definition.

Path, relative to the Jenkins workspace root, to a file containing the Kubernetes application definition.

ID to assign to the created Cloudify deployment. If not provided, one will be randomly generated. You can obtain the deployment ID from the "environment data" output file.

If checked, then the created environment's data will be printed to the job's log.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

Path to a file that will contain the created environment's data. If not provided, the environment data won't be written.

A YAML/JSON file containing GCP service account details, to use for authentication against GCP.

This parameter is optional, and is only relevant for authenticating against GCP.

If provided, it should follow the same layout as described in the "GCP Credentials ID" parameter.

The ID of the credentials to be used for authentication against GCP.

This parameter is optional, and is only relevant for authenticating against GCP.

If provided, it should be the ID of either a string-type or file-type credentials entry, with the standard GCP service account YAML/JSON syntax:

{
  "type": "...",
  "project_id": "...",
  "private_key_id": "...",
  "private_key": "...",
  "client_email": "...",
  "client_id": "...",
  "auth_uri": "...",
  "token_uri": "...",
  "auth_provider_x509_cert_url": "...",
  "client_x509_cert_url": "..."
}
	

The Kubernetes master host to use. This can also be provided through the API Options field; it is available as a separate parameter for convenience.

The application's namespace. Note: value provided here will overwrite the namespace value in the options field, if exists.

Kubernetes options.

Path, relative to the Jenkins workspace root, to a file containing Kubernetes options.

Path, relative to the workspace's root, of a file containing the certificate presented to the Kubernetes host.

Path, relative to the workspace's root, of a file containing the key for the certificate presented to the Kubernetes host.

If checked, then the status of the Kubernetes application is validated after provisioning.

Path to the inputs file to be created.

A JSON containing mapping between outputs/capabilities and inputs. For information about the structure, refer to the tooltip of this build step.

A JSON containing mapping between outputs/capabilities and inputs. For information about the structure, refer to the tooltip of this build step.

Location of the outputs JSON file, containing outputs and capabilities of another deployment. The file must be in the following format:

{
    "outputs": {
    	"<output_name>": "<output_value>",
    	"<output_name>": "<output_value>",
    	...
    },
    "capabilities": {
    	"<capability_name>": "<capability_value>",
    	"<capability_name>": "<capability_value>",
    	...
    }
}
	

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

ID to assign to the created Cloudify deployment. If not provided, one will be randomly generated. You can obtain the deployment ID from the "environment data" output file.

If checked, then the created environment's data will be printed to the job's log.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

Path to a file that will contain the created environment's data. If not provided, the environment data won't be written.

YAML/JSON containing environment variables to pass to the Terraform process. The provided string will be expanded for environment variables (${VAR_NAME}).

Path, relative to the Jenkins workspace root, of a YAML/JSON file containing environment variables to pass to the Terraform process.

Path, on Cloudify Manager, of the Terraform executable. If omitted, the value of the terraform_executable Cloudify secret will be used.

Path, on Cloudify Manager, of Terraform's plugins directory. If omitted, the value of the terraform_plugins_dir Cloudify secret will be used.

Path, on Cloudify Manager, of Terraform's storage directory. If omitted, the value of the terraform_storage_dir Cloudify secret will be used.

URL of the Terraform template. May be a ZIP, tar.gz, or a Git repository.

YAML/JSON containing variables to pass to the Terraform template. The provided string will be expanded for environment variables (${VAR_NAME}).

Path, relative to the Jenkins workspace root, of a YAML/JSON file containing parmaeters to pass to the template.

Path (relative to the workspace root) of the blueprint archive.

URL of the blueprint archive.

ID to assign to the uploaded blueprint.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

Name of the YAML file containing the main entry point to the blueprint.

Directory where the blueprint is located.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

Location where the plugin information, in JSON format, will be stored.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.

URL of the Wagon file.

URL of the plugin.yaml file of the plugin.

URL to the blueprint's archive.

For newly uploaded blueprints, this will be the new blueprint's ID.

For existing blueprints, this should be the existing blueprint's ID.

The name of the YAML file that is to be considered the blueprint's main YAML.

In order to use an existing blueprint, leave this field blank.

The path, relative to the build's workspace, to the new blueprint's root.

In order to use an existing blueprint, leave this field blank.

The ID of the credentials to use when accessing Cloudify. Parameters' expansion is supported when using freestyle jobs.

If checked, then printed Cloudify events and logs will include debug-level records.

ID of the deployment to create.

If checked, then the Cloudify deployment inputs are echoed to the Jenkins log.

At the end of the build step, print the outputs and capabilities to the console.

Inputs to pass to the new deployment, in YAML/JSON format.

Inputs provided here will be merged with inputs provided through a file.

A path, relative to the workspace's root, to a YAML/JSON file containing inputs for the new deployment.

Inputs provided here will be merged with inputs provided through text.

A path, relative to the workspace's root, to a JSON file that will contain the outputs and capabilities of the new deployment.

If not provided, the file won't be created.

Cloudify tenant to operate on. If left empty, then the default tenant (defined in the plugin's configuration page) will be used.