Merge pull request #125 from CiscoDevNet/develop

Develop

docs/data-sources/device_cluster.md

@@ -0,0 +1,39 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "fmc_device_cluster Data Source - terraform-provider-fmc"
+subcategory: ""
+description: |-
+  Data source for FTD Device Cluster in FMC
+  An example is shown below:
+  hcl
+  data "fmc_device_cluster" "cluster" {
+      name = "ftd-cluster1"
+  }
+---
+
+# fmc_device_cluster (Data Source)
+
+Data source for FTD Device Cluster in FMC
+
+An example is shown below: 
+```hcl
+data "fmc_device_cluster" "cluster" {
+	name = "ftd-cluster1"
+}
+```
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `name` (String) Name of the cluster
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+- `type` (String) Type of this resource
+
+

docs/data-sources/device_physical_interfaces.md

@@ -7,6 +7,7 @@ description: |-
   An example is shown below:
   hcl
   data "fmc_device_physical_interfaces" "test-phy-interfaces" {
+      device_id = "<ID of the ftd>"
       name = "TEST-PHY"
   }
 ---
@@ -18,6 +19,7 @@ Data source for Physical Interfaces in FMC
 An example is shown below: 
 ```hcl
 data "fmc_device_physical_interfaces" "test-phy-interfaces" {
+	device_id = "<ID of the ftd>"
 	name = "TEST-PHY"
 }
 ```

docs/data-sources/device_subinterfaces.md

@@ -0,0 +1,48 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "fmc_device_subinterfaces Data Source - terraform-provider-fmc"
+subcategory: ""
+description: |-
+  Data source for Sub-Interfaces in FMC
+  An example is shown below:
+  hcl
+  data "fmc_device_subinterfaces" "sub_interfaces" {
+      device_id = "<ID of the ftd>"
+      subinterface_id = 1
+  }
+---
+
+# fmc_device_subinterfaces (Data Source)
+
+Data source for Sub-Interfaces in FMC
+
+An example is shown below: 
+```hcl
+data "fmc_device_subinterfaces" "sub_interfaces" {
+	device_id = "<ID of the ftd>"
+	subinterface_id = 1
+}
+```
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `device_id` (String) The ID of the device this resource needs
+- `subinterface_id` (Number) ID of sub interface
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+- `if_name` (String) SubInterface logical name
+- `ipv4_static_address` (String) IPv4 Static address
+- `mode` (String) The mode of this resource
+- `mtu` (Number) SubInterface MTU
+- `security_zone_id` (String) Security Zone ID
+- `type` (String) SubInterface type
+- `vlan_id` (Number) The Vlan ID needed for this resource
+
+

docs/data-sources/port_group_objects.md

@@ -0,0 +1,38 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "fmc_port_group_objects Data Source - terraform-provider-fmc"
+subcategory: ""
+description: |-
+  Data source for Port Group Objects in FMC
+  An example is shown below:
+  hcl
+  data "fmc_port_group_objects" "test" {
+      name = "test-object-group"
+  }
+---
+
+# fmc_port_group_objects (Data Source)
+
+Data source for Port Group Objects in FMC
+
+An example is shown below: 
+```hcl
+data "fmc_port_group_objects" "test" {
+	name = "test-object-group"
+}
+```
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `name` (String) Name of the port group object
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+

docs/resources/device_cluster.md

@@ -0,0 +1,220 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "fmc_device_cluster Resource - terraform-provider-fmc"
+subcategory: ""
+description: |-
+  Resource for adding device in a cluster
+  Note: this will only work on VMware, not on public cloud.
+  Example
+  An example is shown below:
+  hcl
+   resource "fmc_device_cluster" "cluster" { 
+      name = "ftd_cluster" 
+      control_device {
+        cluster_node_bootstrap {
+          priority = 1
+          cclip = "10.10.11.1"
+        }
+        device_details  {
+          id = data.fmc_devices.device1.id
+          name = data.fmc_devices.device1.name
+        }
+      }
+      common_bootstrap {
+        ccl_interface {
+          id = data.fmc_device_physical_interfaces.ccl_physical_interface.id
+          name = data.fmc_device_physical_interfaces.ccl_physical_interface.name
+        }
+        ccl_network = "10.10.11.0/27"
+        vni_network = "10.10.10.0/27"
+      }
+      data_devices{
+          cluster_node_bootstrap{
+            priority = 2
+            cclip = "10.10.11.2"
+          }
+          device_details{
+            id = data.fmc_devices.device2.id
+            name = data.fmc_devices.device2.name
+          }
+      }
+      data_devices{
+          cluster_node_bootstrap{
+            priority = 3
+            cclip = "10.10.11.3"
+          }
+          device_details{
+            id = data.fmc_devices.device3.id
+            name = data.fmc_devices.device3.name
+          }
+      }
+    }
+  **Note:** This feature is only supported for VMWare cloud platform.
+  **Note:** If creating multiple rules during a single `terraform apply`, remember to use `depends_on` to chain the rules so that terraform creates it in the same order that you intended.
+  **Note:** Deleting a cluster will delete all it's data nodes with control node as well.
+---
+
+# fmc_device_cluster (Resource)
+
+Resource for adding device in a cluster
+
+**Note: this will only work on VMware, not on public cloud.**
+## Example
+An example is shown below: 
+```hcl
+ resource "fmc_device_cluster" "cluster" { 
+	name = "ftd_cluster" 
+	control_device {
+	  cluster_node_bootstrap {
+		priority = 1
+		cclip = "10.10.11.1"
+	  }
+	  device_details  {
+		id = data.fmc_devices.device1.id
+		name = data.fmc_devices.device1.name
+	  }
+	}
+	common_bootstrap {
+	  ccl_interface {
+		id = data.fmc_device_physical_interfaces.ccl_physical_interface.id
+		name = data.fmc_device_physical_interfaces.ccl_physical_interface.name
+	  }
+	  ccl_network = "10.10.11.0/27"
+	  vni_network = "10.10.10.0/27"
+	}
+	data_devices{
+		cluster_node_bootstrap{
+		  priority = 2
+		  cclip = "10.10.11.2"
+		}
+		device_details{
+		  id = data.fmc_devices.device2.id
+		  name = data.fmc_devices.device2.name
+		}
+	}
+	data_devices{
+		cluster_node_bootstrap{
+		  priority = 3
+		  cclip = "10.10.11.3"
+		}
+		device_details{
+		  id = data.fmc_devices.device3.id
+		  name = data.fmc_devices.device3.name
+		}
+	}
+  }
+**Note:** This feature is only supported for VMWare cloud platform.
+**Note:** If creating multiple rules during a single `terraform apply`, remember to use `depends_on` to chain the rules so that terraform creates it in the same order that you intended.
+**Note:** Deleting a cluster will delete all it's data nodes with control node as well.
+```
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `common_bootstrap` (Block List, Min: 1) Control device information (see [below for nested schema](#nestedblock--common_bootstrap))
+- `control_device` (Block List, Min: 1) Control device information (see [below for nested schema](#nestedblock--control_device))
+
+### Optional
+
+- `data_devices` (Block List, Max: 500) Data device information (see [below for nested schema](#nestedblock--data_devices))
+- `name` (String) The name of cluster
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+- `type` (String) The type of this resource
+
+<a id="nestedblock--common_bootstrap"></a>
+### Nested Schema for `common_bootstrap`
+
+Optional:
+
+- `ccl_interface` (Block List) (see [below for nested schema](#nestedblock--common_bootstrap--ccl_interface))
+- `ccl_network` (String) Cluster control network
+- `vni_network` (String) VNI network
+
+<a id="nestedblock--common_bootstrap--ccl_interface"></a>
+### Nested Schema for `common_bootstrap.ccl_interface`
+
+Optional:
+
+- `id` (String) Interface ID
+- `name` (String) Interface Name
+
+Read-Only:
+
+- `type` (String) Interface Type
+
+
+
+<a id="nestedblock--control_device"></a>
+### Nested Schema for `control_device`
+
+Required:
+
+- `cluster_node_bootstrap` (Block List, Min: 1) (see [below for nested schema](#nestedblock--control_device--cluster_node_bootstrap))
+- `device_details` (Block List, Min: 1) (see [below for nested schema](#nestedblock--control_device--device_details))
+
+<a id="nestedblock--control_device--cluster_node_bootstrap"></a>
+### Nested Schema for `control_device.cluster_node_bootstrap`
+
+Required:
+
+- `cclip` (String) Cluster control IP
+
+Optional:
+
+- `priority` (Number) Set the priority of cluster node
+
+
+<a id="nestedblock--control_device--device_details"></a>
+### Nested Schema for `control_device.device_details`
+
+Required:
+
+- `id` (String) Device ID
+
+Optional:
+
+- `name` (String) Device Name
+
+Read-Only:
+
+- `type` (String) Device Type
+
+
+
+<a id="nestedblock--data_devices"></a>
+### Nested Schema for `data_devices`
+
+Optional:
+
+- `cluster_node_bootstrap` (Block List) (see [below for nested schema](#nestedblock--data_devices--cluster_node_bootstrap))
+- `device_details` (Block List) (see [below for nested schema](#nestedblock--data_devices--device_details))
+
+<a id="nestedblock--data_devices--cluster_node_bootstrap"></a>
+### Nested Schema for `data_devices.cluster_node_bootstrap`
+
+Optional:
+
+- `cclip` (String) Cluster control IP
+- `priority` (Number) Set the priority of cluster node
+
+
+<a id="nestedblock--data_devices--device_details"></a>
+### Nested Schema for `data_devices.device_details`
+
+Optional:
+
+- `id` (String) Device ID
+- `name` (String) Device Name
+
+Read-Only:
+
+- `type` (String) Device Type
+
+