zenlayercloud

Overview ¶

Use this data source to query instances types.

Example Usage ¶

```hcl data "zenlayercloud_bmc_instance_types" "foo" {

}

data "zenlayercloud_bmc_instance_types" "sel" {
  availability_zone    = "SEL-A"
  instance_charge_type = "PREPAID"
  exclude_sold_out     = true
}

```

Use this data source to query DDoS IP instances.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_ddos_ips" "foo" {
	availability_zone = "SEL-A"
}

```

Use this data source to query eip instances.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_eips" "foo" {
	availability_zone = "SEL-A"
}

```

Use this data source to query images.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_images" "foo" {
	catalog = "centos"
    instance_type_id = "S9I"
}

```

Use this data source to query information about BMC instance hardware health status.

~> **NOTE:** Different hardware vendors use different starting indices for CPU numbering (some start from 0, others from 1). The attribute names (e.g., cpu0_temp, cpu1_temp, cpu2_temp) retain the original vendor's numbering style.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_instance_health_status" "foo" {
  instance_id = "<instanceId>"
}

```

Use this data source to query bmc instances.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_instances" "foo" {
  availability_zone = "SEL-A"
}

```

Use this data source to query vpc subnets information.

Example Usage ¶

```hcl

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_bmc_subnet" "foo" {
  availability_zone = var.availability_zone
  name       		= "subnet_test"
  cidr_block 		= "10.0.0.0/16"
}

data "zenlayercloud_bmc_subnets" "id_subnets" {
  subnet_id = zenlayercloud_bmc_subnet.foo.id
}

data "zenlayercloud_bmc_subnets" "name_subnets" {
  subnet_name = zenlayercloud_bmc_subnet.foo.name
}

```

Use this data source to get the available regions for vpc.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_vpc_regions" "sel-region" {
  availability_zone = "SEL-A"
}

```

Use this data source to query vpc information.

Example Usage ¶

```hcl data "zenlayercloud_bmc_vpc_regions" "region" { }

resource "zenlayercloud_bmc_vpc" "foo" {
  region     = data.zenlayercloud_bmc_vpc_regions.region.vpc_regions.0.region
  name       = "test_vpc"
  cidr_block = "10.0.0.0/16"
}

data "zenlayercloud_bmc_vpcs" "foo" { } ```

Use this data source to get all bmc available zones.

Example Usage ¶

```hcl data "zenlayercloud_bmc_zones" "all" { }

data "zenlayercloud_bmc_zones" "sel" {
	name_regex = "SEL*"
}

```

Use this data source to query cloud regions.

Example Usage ¶

```hcl

data "zenlayercloud_sdn_cloud_regions" "google_regions" {
	cloud_type = "GOOGLE"
}

```

Use this data source to query layer 3 cloud routers.

Example Usage ¶

```hcl data "zenlayercloud_sdn_cloud_routers" "all" {

}

```

Use this data source to get all sdn data centers available.

Example Usage ¶

```hcl data "zenlayercloud_sdn_datacenters" "all" { }

data "zenlayercloud_sdn_datacenters" "sel" {
	name_regex = "SEL*"
}

```

Use this data source to query datacenter ports.

Example Usage ¶

```hcl

data "zenlayercloud_sdn_ports" "foo" {
	datacenter = "SIN1"
}

```

Use this data source to query layer 2 private connect.

Example Usage ¶

```hcl data "zenlayercloud_sdn_private_connects" "all" {

}

data "zenlayercloud_sdn_private_connects" "byIds" {
	connect_ids = ["xxxxxxx"]
}

```

Use this data source to get all zga available accelerate regions by origin_region_id.

Example Usage ```hcl

data "zenlayercloud_zga_origin_regions" "DE" {
	name_regex = "DE"
}

data "zenlayercloud_zga_accelerate_regions" "all" {
	origin_region_id = data.zenlayercloud_zga_origin_regions.DE.regions.0.id
}

data "zenlayercloud_zga_accelerate_regions" "FR" {
	origin_region_id = "FR"
	name_regex = "US*"
}

```

Use this data source to get all zga accelerator.

Example Usage ```hcl data "zenlayercloud_zga_accelerators" "all" { } ```

Use this data source to get all zga certificates.

Example Usage ```hcl data "zenlayercloud_zga_certificates" "all" { } ```

Use this data source to get all zga available origin regions.

Example Usage ```hcl

data "zenlayercloud_zga_origin_regions" "all" {
}

data "zenlayercloud_zga_origin_regions" "fr" {
	name_regex = "FR*"
}

```

Use this data source to query vm disk information.

Example Usage ¶

```hcl data "zenlayercloud_zvm_disks" "all" { }

filter system disk ¶

data "zenlayercloud_zvm_disks" "system_disk" {
  disk_type = "SYSTEM"
}

#filter with name regex

data "zenlayercloud_zvm_disks" "name_disk" {
  name_regex = "disk20*"
}

```

Use this data source to query images.

Example Usage ¶

```hcl

data "zenlayercloud_zvm_images" "foo" {
	availability_zone = "FRA-A"
    category = "CentOS"
	image_type = ["PUBLIC_IMAGE"]
}

```

Use this data source to query instances type.

Example Usage ¶

```hcl data "zenlayercloud_zvm_instance_types" "foo" {

}

data "zenlayercloud_zvm_instance_types" "sel1c1g" {
  availability_zone = "SEL-A"
  cpu_count   		= 1
  memory	        = 1
}

```

Use this data source to query detailed information of security groups.

Example Usage ¶

```hcl data "zenlayercloud_zvm_security_groups" "sg1" { }

data "zenlayercloud_zvm_security_groups" "sg2" {
  name = "example_name"
}

```

Use this data source to query subnets information.

Example Usage ¶

```hcl

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_zvm_subnet" "foo" {
  availability_zone = var.availability_zone
  name       		= "subnet_test"
  cidr_block 		= "10.0.0.0/24"
}

filter by subnet id ¶

data "zenlayercloud_zvm_subnets" "id_subnets" {
  subnet_id = zenlayercloud_zvm_subnet.foo.id
}

filter by subnet name ¶

data "zenlayercloud_zvm_subnets" "name_subnets" {
  subnet_name = zenlayercloud_zvm_subnet.foo.name
}

```

Use this data source to get all vm available zones.

Example Usage ¶

```hcl data "zenlayercloud_zvm_zones" "all" { }

data "zenlayercloud_zvm_zones" "sel" {
	name_regex = "SEL*"
}

```

The ZenlayerCloud provider is used to interact with many resources supported by [ZenlayerCloud](https://console.zenlayer.com). The provider needs to be configured with the proper credentials before it can be used.

Use the navigation on the left to read about the available resources.

Example Usage ¶

```hcl

terraform {
  required_providers {
	zenlayercloud = {
	  source = "zenlayer/zenlayercloud"
	}
  }
}

Configure the Zenlayer Cloud Provider ¶

provider "zenlayercloud" {
  access_key_id       =  var.access_key_id
  access_key_password =  var.access_key_password
}

```

Resources List ¶

Provider Data Sources ¶

Zenlayer Virtual Machine(ZVM)

  Data Source
	zenlayercloud_zvm_zones
	zenlayercloud_zvm_images
	zenlayercloud_zvm_instance_types
	zenlayercloud_zvm_security_groups
	zenlayercloud_zvm_instance_types
	zenlayercloud_zvm_disks
	zenlayercloud_zvm_subnets

  Resource
	zenlayercloud_zvm_image
	zenlayercloud_zvm_security_group
	zenlayercloud_zvm_security_group_attachment
	zenlayercloud_zvm_security_group_rule
	zenlayercloud_zvm_instance
	zenlayercloud_zvm_disk
	zenlayercloud_zvm_disk_attachment
	zenlayercloud_zvm_subnet

Bare Metal Cloud(BMC)

  Data Source
	zenlayercloud_bmc_zones
	zenlayercloud_bmc_instance_types
    zenlayercloud_bmc_images
	zenlayercloud_bmc_instances
	zenlayercloud_bmc_instance_health_status
	zenlayercloud_bmc_eips
	zenlayercloud_bmc_vpc_regions
	zenlayercloud_bmc_vpcs
	zenlayercloud_bmc_subnets

  Resource
	zenlayercloud_bmc_instance
	zenlayercloud_bmc_eip
	zenlayercloud_bmc_eip_association
	zenlayercloud_bmc_vpc
	zenlayercloud_bmc_subnet

Cloud Networking(SDN)

  Data Source
	zenlayercloud_sdn_datacenters
	zenlayercloud_sdn_ports
	zenlayercloud_sdn_private_connects
	zenlayercloud_sdn_cloud_regions
  Resource
	zenlayercloud_sdn_port
	zenlayercloud_sdn_private_connect

Zenlayer Global Accelerator(ZGA)

  Data Source
 	zenlayercloud_zga_certificates
	zenlayercloud_zga_origin_regions
	zenlayercloud_zga_accelerate_regions
	zenlayercloud_zga_accelerators

  Resource
	zenlayercloud_zga_certificate
	zenlayercloud_zga_accelerator

Zenlayer Elastic Compute(ZEC)

  Data Source
	zenlayercloud_zec_vpcs
	zenlayercloud_zec_vpc_routes
	zenlayercloud_zec_subnets
	zenlayercloud_zec_dhcp_options_sets
	zenlayercloud_zec_images
	zenlayercloud_zec_disks
	zenlayercloud_zec_disk_snapshots
	zenlayercloud_zec_disk_snapshot_policies
	zenlayercloud_zec_cidrs
	zenlayercloud_zec_eips
	zenlayercloud_zec_instances
	zenlayercloud_zec_vnics
	zenlayercloud_zec_nat_gateways
	zenlayercloud_zec_nat_gateway_snats
	zenlayercloud_zec_nat_gateway_dnats
	zenlayercloud_zec_border_gateways

  Resource
	zenlayercloud_zec_vpc
	zenlayercloud_zec_security_group
	zenlayercloud_zec_security_group_rule_set
	zenlayercloud_zec_vpc_security_group_attachment
	zenlayercloud_zec_vpc_route
	zenlayercloud_zec_subnet
	zenlayercloud_zec_dhcp_options_set
	zenlayercloud_zec_dhcp_options_set_attachment
	zenlayercloud_zec_vnic
	zenlayercloud_zec_vnic_attachment
	zenlayercloud_zec_vnic_ipv4
	zenlayercloud_zec_cidr
	zenlayercloud_zec_eip
	zenlayercloud_zec_eip_association
	zenlayercloud_zec_instance
	zenlayercloud_zec_disk
	zenlayercloud_zec_disk_attachment
	zenlayercloud_zec_disk_snapshot
	zenlayercloud_zec_disk_snapshot_policy
	zenlayercloud_zec_disk_snapshot_policy_attachment
	zenlayercloud_zec_nat_gateway
	zenlayercloud_zec_nat_gateway_snat
	zenlayercloud_zec_nat_gateway_dnat

Zenlayer Load Balancing(ZLB)

  Data Source
	zenlayercloud_zlb_regions
	zenlayercloud_zlb_instances
	zenlayercloud_zlb_listeners
	zenlayercloud_zlb_backends

  Resource
	zenlayercloud_zlb_instance
	zenlayercloud_zlb_listener
	zenlayercloud_zlb_backend

Zenlayer Private DNS(ZDNS)

  Data Source
	zenlayercloud_zdns_zones
	zenlayercloud_zdns_zone_records

  Resource
	zenlayercloud_zdns_zone
	zenlayercloud_zdns_zone_record
	zenlayercloud_zdns_zone_vpc_set_attachment

Traffic

  Data Source
	zenlayercloud_traffic_bandwidth_cluster_areas
	zenlayercloud_traffic_bandwidth_clusters

  Resource
	zenlayercloud_traffic_bandwidth_cluster

Keypair

  Data Source
	zenlayercloud_key_pairs

  Resource
	zenlayercloud_key_pair

Provides an DDoS IP resource.

Example Usage ¶

```hcl

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_bmc_ddos_ip" "foo" {
  availability_zone = var.availability_zone
}

```

Import ¶

EIP can be imported using the id, e.g.

``` $ terraform import zenlayercloud_bmc_ddos_ip.foo 123123xxxx ```

Provides an DDoS IP resource associated with BMC instance.

Example Usage ¶

```hcl

resource "zenlayercloud_bmc_ddos_ip_association" "foo" {
  ddos_ip_id      = "ddosIpIdxxxxxx"
  instance_id = "instanceIdxxxxxx"
}

```

Import ¶

DDoS IP association can be imported using the id, e.g.

``` $ terraform import zenlayercloud_bmc_ddos_ip_association.bar ddosIpIdxxxxxx:instanceIdxxxxxxx ```

Provides an EIP resource.

Example Usage ¶

```hcl

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_bmc_eip" "foo" {
  availability_zone = var.availability_zone
  tags = {
    "group"  = "test"
  }
}

```

Import ¶

EIP can be imported using the id, e.g.

``` $ terraform import zenlayercloud_bmc_eip.foo 123123xxxx ```

Provides an eip resource associated with BMC instance.

Example Usage ¶

```hcl

resource "zenlayercloud_bmc_eip_association" "foo" {
  eip_id      = "eipxxxxxx"
  instance_id = "instanceIdxxxxxx"
}

```

Import ¶

Eip association can be imported using the id, e.g.

``` $ terraform import zenlayercloud_bmc_eip_association.bar eipIdxxxxxx:instanceIdxxxxxxx ```

Provides a BMC instance resource.

~> **NOTE:** You can launch an BMC instance for a private network via specifying parameter `subnet_id`.

~> **NOTE:** At present, 'PREPAID' instance cannot be deleted. Executing terraform destroy will only cancel the subscription, and the instance will not be immediately destroyed. It will be automatically destroyed after expiration.

Example Usage ¶

```hcl

data "zenlayercloud_bmc_zones" "default" {

}

data "zenlayercloud_bmc_instance_types" "default" {
  availability_zone = data.zenlayercloud_bmc_zones.default.zones.0.id
}

Get a centos image which also supported to install on given instance type ¶

data "zenlayercloud_bmc_images" "default" {
  catalog          = "centos"
  instance_type_id = data.zenlayercloud_bmc_instance_types.default.instance_types.0.id
}

resource "zenlayercloud_bmc_subnet" "default" {
  availability_zone = data.zenlayercloud_bmc_zones.default.zones.0.id
  name              = "test-subnet"
  cidr_block        = "10.0.10.0/24"
}

Create a web server ¶

resource "zenlayercloud_bmc_instance" "web" {
  availability_zone    = data.zenlayercloud_bmc_zones.default.zones.0.id
  image_id             = data.zenlayercloud_bmc_images.default.images.0.image_id
  internet_charge_type = "ByBandwidth"
  instance_type_id     = data.zenlayercloud_bmc_instance_types.default.instance_types.0.id
  password             = "Example~123"
  instance_name        = "web"
  subnet_id            =  zenlayercloud_bmc_subnet.default.id
  tags = {
	"group"  = "test"
  }
}

```

Import ¶

BMC instance can be imported using the id, e.g.

``` terraform import zenlayercloud_bmc_instance.foo 123123xxx ```

Provide a resource to create a VPC subnet.

Example Usage ¶

```hcl

variable "region" {
  default = "SEL1"
}

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_bmc_vpc" "foo" {
  region	 = var.region
  name       = "test-vpc"
  cidr_block = "10.0.0.0/16"
}

resource "zenlayercloud_bmc_subnet" "subnet_with_vpc" {
  availability_zone = var.availability_zone
  name              = "test-subnet"
  vpc_id            = zenlayercloud_bmc_vpc.foo.id
  cidr_block        = "10.0.10.0/24"
}

resource "zenlayercloud_bmc_subnet" "subnet" {
  availability_zone = var.availability_zone
  name              = "test-subnet"
  cidr_block        = "10.0.10.0/24"
}

```

Import ¶

Vpc subnet instance can be imported, e.g.

``` $ terraform import zenlayercloud_bmc_subnet.subnet subnet_id ```

Provide a resource to create a VPC.

Example Usage ¶

```hcl data "zenlayercloud_bmc_vpc_regions" "default_region" {

}

resource "zenlayercloud_bmc_vpc" "foo" {
  region 	 = data.zenlayercloud_bmc_vpc_regions.default_region.regions.0.id
  cidr_block = "10.0.0.0/26"
  tags = {
    "group"  = "test"
  }
}

```

Import ¶

Vpc instance can be imported, e.g.

``` $ terraform import zenlayercloud_bmc_vpc.test vpc-id ```

Provides a resource to manage datacenter port.

Example Usage ¶

```hcl

resource "zenlayercloud_sdn_port" "foo" {
  name       			= "my_name"
  datacenter    		= "xxxxx-xxxxx-xxxxx"
  remarks				= "Test"
  port_type				= "1G"
  business_entity_name  = "John"
}

```

Import ¶

Port can be imported, e.g.

``` $ terraform import zenlayercloud_sdn_port.foo xxxxxx ```

Provides a resource to manage layer 2 private connect.

Example Usage ¶

```hcl

resource "zenlayercloud_sdn_private_connect" "aws-port-test" {
  connect_name       	= "Test"
  connect_bandwidth    	= 20
  endpoints	{
    port_id = "xxxxxxxxx"
    endpoint_type = "TENCENT"
    vlan_id = "1019"
	}
  endpoints {
    datacenter = "SOF1"
    cloud_region = "eu-west-1"
    cloud_account = "123412341234"
    endpoint_type = "AWS"
    vlan_id = "1457"
  }

resource "zenlayercloud_sdn_private_connect" "aws-tencent-test" {
  connect_name       	= "Test"
  connect_bandwidth    	= 20
  endpoints	{
    datacenter = "HKG2"
    cloud_region = "ap-hongkong-a-kc"
    cloud_account = "123412341234"
    endpoint_type = "TENCENT"
    vlan_id = "1019"
	}
  endpoints {
    datacenter = "SOF1"
    cloud_region = "eu-west-1"
    cloud_account = "123412341234"
    endpoint_type = "AWS"
    vlan_id = "1457"
  }

```

Import ¶

Private Connect can be imported, e.g.

``` $ terraform import zenlayercloud_sdn_private_connect.foo xxxxxx ```

Provides a accelerator resource.

~> **NOTE:** Only L4 listener can be configured when domain is null.

~> **NOTE:** The Domain is not allowed to be the same as origin, otherwise a loop will be formed, making acceleration unusable.

Example Usage ```hcl

resource "zenlayercloud_zga_certificate" "default" {
	certificate  = <<EOF

-----BEGIN CERTIFICATE----- [......] # cert contents -----END CERTIFICATE----- EOF

key = <<EOF

-----BEGIN RSA PRIVATE KEY----- [......] # key contents -----END RSA PRIVATE KEY----- EOF

	lifecycle {
		create_before_destroy = true
	}
}

resource "zenlayercloud_zga_accelerator" "default" {
  accelerator_name = "accelerator_test"
  charge_type = "ByTrafficPackage"
  domain = "test.com"
  relate_domains = ["a.test.com"]
  origin_region_id = "DE"
  origin = ["10.10.10.10"]
  backup_origin = ["10.10.10.14"]
  certificate_id = resource.zenlayercloud_zga_certificate.default.id
  accelerate_regions {
    accelerate_region_id = "KR"
  }
  accelerate_regions {
    accelerate_region_id = "US"
  }
  l4_listeners {
    protocol = "udp"
    port_range = "53/54"
    back_port_range = "53/54"
  }
  l4_listeners {
    port = 80
    back_port = 80
    protocol = "tcp"
  }
  l7_listeners {
    port = 443
    back_port = 80
    protocol = "https"
    back_protocol = "http"
  }
  l7_listeners {
    port_range = "8888/8890"
    back_port_range = "8888/8890"
    protocol = "http"
    back_protocol = "http"
  }
  protocol_opts {
    websocket = true
    gzip = false
  }
  access_control {
    enable = true
    rules {
      listener = "https:443"
      directory = "/"
      policy = "deny"
      cidr_ip = ["10.10.10.10"]
    }
    rules {
      listener = "udp:53/54"
      directory = "/"
      policy = "accept"
      cidr_ip = ["10.10.10.11/8"]
    }
  }
}

``` Import

Accelerator can be imported using the id, e.g.

``` terraform import zenlayercloud_zga_accelerator.default acceleratorId ```

Provides a certificate resource.

~> **NOTE:** Modification of the certificate and key is not supported. If you want to change it, you need to create a new certificate.

~> **NOTE:** When the certificate and key are set to empty strings, the Update will not take effect.

Example Usage ```hcl

resource "zenlayercloud_zga_certificate" "default" {
	certificate  = <<EOF

-----BEGIN CERTIFICATE----- [......] # cert contents -----END CERTIFICATE----- EOF

key = <<EOF

-----BEGIN RSA PRIVATE KEY----- [......] # key contents -----END RSA PRIVATE KEY----- EOF

	label = "certificate"

	lifecycle {
		create_before_destroy = true
	}
}

``` Import

Certificate can be imported using the id, e.g.

``` terraform import zenlayercloud_zga_certificate.default certificateId ```

Provide a resource to create data disk.

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_disk" "foo" {
  availability_zone 	 = "SEL-A"
  name  				 = "SEL-20G"
  disk_size				 = 20
  tags = {
    "group"  = "test"
  }
}

```

Import ¶

Disk instance can be imported, e.g.

``` $ terraform import zenlayercloud_zvm_disk.test disk-id ```

Provide a resource to attach a disk to an instance.

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_disk_attachment" "foo" {
  disk_id 	 	= "diskxxxx"
  instance_id  	= "instancexxxx"
}

```

Import ¶

Disk attachment can be imported, e.g.

``` $ terraform import zenlayercloud_zvm_disk_attachment.foo disk-id:instance-id ```

Provides a resource to manage image.

~> **NOTE:** You have to keep the instance power off if the image is created from instance.

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_image" "foo" {
  image_name       	= "web-image-centos"
  instance_id    	= "xxxxxx"
  image_description	= "create a image by the web server"
}

```

Import ¶

Image can be imported, e.g.

``` $ terraform import zenlayercloud_zvm_image.foo img-xxxxxxx ```

Provides a instance resource.

~> **NOTE:** You can launch an instance for a private network via specifying parameter `subnet_id`.

~> **NOTE:** At present, 'PREPAID' instance cannot be deleted and must wait it to be outdated and released automatically.

Example Usage ¶

```hcl

data "zenlayercloud_zvm_zones" "default" {

}

data "zenlayercloud_zvm_instance_types" "default" {
  availability_zone = data.zenlayercloud_zvm_zones.default.zones.0.id
}

Get a centos image which also supported to install on given instance type ¶

data "zenlayercloud_zvm_images" "default" {
  availability_zone = data.zenlayercloud_zvm_zones.default.zones.0.id
  category          = "CentOS"
}

resource "zenlayercloud_zvm_subnet" "default" {
  name              = "test-subnet"
  cidr_block        = "10.0.10.0/24"
}

Create a web server ¶

resource "zenlayercloud_zvm_instance" "web" {
  availability_zone    = data.zenlayercloud_zvm_zones.default.zones.0.id
  image_id             = data.zenlayercloud_zvm_images.default.images.0.image_id
  internet_charge_type = "ByBandwidth"
  instance_type        = data.zenlayercloud_zvm_instance_types.default.instance_types.0.id
  password             = "Example~123"
  instance_name        = "web"
  subnet_id            = zenlayercloud_zvm_subnet.default.id
  system_disk_size     = 100
  tags = {
    "group"  = "web"
  }
}

```

Import ¶

Instance can be imported using the id, e.g.

``` terraform import zenlayercloud_zvm_instance.foo 123123xxx ```

Provides a resource to create security group.

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_security_group" "foo" {
  name       	= "example-name"
  description	= "example purpose"
}

```

Import ¶

Security group can be imported, e.g.

``` $ terraform import zenlayercloud_zvm_security_group.security_group security_group_id ```

Provides a resource to create a security group attachment ¶

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_security_group_attachment" "foo" {
  security_group_id = "12364246"
  instance_id       = "62343412426423623"
}

```

Import ¶

Security group attachment can be imported using the id, e.g.

``` terraform import zenlayercloud_zvm_security_group_attachment.security_group_attachment securityGroupId:instanceId ```

Provides a resource to create security group rule.

~> **NOTE:** Single security rule is hardly ordered, use zenlayercloud_zvm_security_group_rule_set instead.

Example Usage ¶

```hcl

resource "zenlayercloud_zvm_security_group" "foo" {
  name        = "example-name"
  description = "example purpose"
}

resource "zenlayercloud_zvm_security_group_rule" "bar" {
  security_group_id = zenlayercloud_zvm_security_group.foo.id
  direction         = "ingress"
  policy            = "accept"
  cidr_ip    		= "10.0.0.0/16"
  ip_protocol       = "tcp"
  port_range        = "80"
}

```

Provide a resource to create a subnet.

Example Usage ¶

```hcl

variable "availability_zone" {
  default = "SEL-A"
}

resource "zenlayercloud_zvm_subnet" "foo" {
  availability_zone	 = var.availability_zone
  name       = "test-subnet"
  cidr_block = "10.0.0.0/24"
}

```

Import ¶

Subnet instance can be imported, e.g.

``` $ terraform import zenlayercloud_zvm_subnet.subnet subnet_id ```