feat: Add candidate subnets field in interconnect attachment (#5)

Author: umairidris

modules/interconnect_attachment/main.tf

@@ -15,16 +15,17 @@
  */
 
 resource "google_compute_interconnect_attachment" "attachment" {
-  name          = var.name
-  router        = var.router
-  project       = var.project
-  region        = var.region
-  interconnect  = var.interconnect
-  admin_enabled = var.admin_enabled
-  type          = var.type
-  description   = var.description
-  bandwidth     = var.bandwidth
-  vlan_tag8021q = var.vlan_tag8021q
+  name              = var.name
+  router            = var.router
+  project           = var.project
+  region            = var.region
+  interconnect      = var.interconnect
+  admin_enabled     = var.admin_enabled
+  type              = var.type
+  description       = var.description
+  bandwidth         = var.bandwidth
+  candidate_subnets = var.candidate_subnets
+  vlan_tag8021q     = var.vlan_tag8021q
 }
 
 module "interface" {

modules/interconnect_attachment/variables.tf

@@ -63,6 +63,12 @@ variable "description" {
   default     = null
 }
 
+variable "candidate_subnets" {
+  type        = list(string)
+  description = "Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc)."
+  default     = null
+}
+
 variable "vlan_tag8021q" {
   type        = string
   description = "The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4094."