When attempting to create meraki_networks_appliance_vlans with reserved_ip_ranges set, it will successfully create the resource, but won't actually set the reserved_ip_ranges.
Expected behavior
I would expect it to create meraki_networks_appliance_vlans with reserved_ip_ranges set.
Repro
resource "meraki_networks_appliance_vlans" "example" {
network_id = "redacted"
appliance_ip = "192.168.2.1"
id = "2"
subnet = "192.168.2.0/24"
name = "guest"
dhcp_handling = "Do not respond to DHCP requests"
dns_nameservers = "upstream_dns"
dhcp_lease_time = "1 day"
dhcp_boot_options_enabled = false
reserved_ip_ranges = [
{ comment: "range1", start: "192.168.2.2", end: "192.168.2.3" }, # Not sent to the api on create
{ comment: "range2", start: "192.168.2.4", end: "192.168.2.5" }, # Not sent to the api on create
{ comment: "range3", start: "192.168.2.6", end: "192.168.2.7" }, # Not sent to the api on create
]
}
Environment (please complete the following information):
Prerequisites
Describe the bug
When attempting to create
meraki_networks_appliance_vlans
withreserved_ip_ranges
set, it will successfully create the resource, but won't actually set thereserved_ip_ranges
.Expected behavior
I would expect it to create
meraki_networks_appliance_vlans
withreserved_ip_ranges
set.Repro
Environment (please complete the following information):
Additional context
I assume this could be a limitation from the api. Create Network Appliance Vlan does not contain
reservedIpRanges
, while Update Network Appliance Vlan does.