» vcd_catalog

Provides a vCloud Director catalog resource. This can be used to create and delete a catalog.

Supported in provider v2.0+

» Example Usage

resource "vcd_catalog" "myNewCatalog" {
  org = "my-org"

  name             = "my-catalog"
  description      = "catalog for files"
  delete_recursive = "true"
  delete_force     = "true"
}

» Argument Reference

The following arguments are supported:

  • org - (Optional) The name of organization to use, optional if defined at provider level. Useful when connected as sysadmin working across different organisations
  • name - (Required) Catalog name
  • description - (Optional) - Description of catalog
  • delete_recursive - (Required) - When destroying use delete_recursive=True to remove the catalog and any objects it contains that are in a state that normally allows removal
  • delete_force -(Required) - When destroying use delete_force=True with delete_recursive=True to remove a catalog and any objects it contains, regardless of their state

» Importing

An existing catalog can be imported into this resource via supplying the full dot separated path for a catalog. For example, using this structure, representing an existing catalog that was not created using Terraform:

resource "vcd_catalog" "my-catalog" {
  org              = "my-org"
  name             = "my-catalog"
  delete_recursive = "true"
  delete_force     = "true"
}

You can import such catalog into terraform state using this command

terraform import vcd_catalog.my-catalog my-org.my-catalog

NOTE: the default separator (.) can be changed using Provider.import_separator or variable VCD_IMPORT_SEPARATOR

After that, you can expand the configuration file and either update or delete the catalog as needed. Running terraform plan at this stage will show the difference between the minimal configuration file and the catalog's stored properties.