The data source for the network object allows you to get the following parameters for an IPv4 network resource:
Parameter | Description | Example |
|---|---|---|
network_view | The network view in which the network exists. | nondefault_netview |
cidr | The network block which corresponds to the network, in CIDR notation. | 192.0.17.0/24 |
| A description of the network. This is a regular comment. | Untrusted network |
| The set of extensible attributes, if any. The content is formatted as a string of JSON map. | {\"Owner\": |
"public internet caffe\"State Library\",\"Administrator\":\"unknown\"} |
To get retrieve information about a network, you must specify the network address in the CIDR formatIPv4 networks that match the specified filters, use the filters argument and specify the parameters mentioned in the below table. These are the searchable parameters of the corresponding object in Infoblox NIOS WAPI. If you do not specify any parameter, the data source retrieves information about all IPv4 networks in the NIOS Grid.
The following table describes the parameters you can define in an infoblox_ipv4_network data source block:
Parameter |
|---|
Alias* | Description | |
|---|---|---|
network | cidr | Specifies the network block that corresponds to the network, in CIDR notation. Do not use the IPv6 CIDR for an IPv4 network. |
|
| Specifies the network view in which the network |
exists. |
default will be used as the network view name.If the network container is in a non-default network view, then you must specify that view.
cidr
Required
matching objects are retrieved from all network views in the NIOS Grid. | ||
|
| Describes the network. |
| Extensible Attributes | - | Specifies the extensible attributes specified for the network. You must specify the key/value pair within the filters argument.Example: filters = {"*Site" = "some test site"} |
*Aliases are the parameter names used in the prior releases of Infoblox IPAM Plug-In for Terraform. Do not use the alias names for parameters in the data source blocks. Using them can result in error scenarios.
Example of an IPv4 Network Data Source Block
resource "infoblox_ipv4_network" "net2" {
cidr = "192.168.128.0/20"
network_view = "nondefault_netview"
reserve_ip = 5
gateway = "192.168.128.254"
comment = "small network for testing"
ext_attrs = jsonencode({
"Site" = "bla-bla-bla... testing..."
})
}
data "infoblox_ipv4_network" "nearby_network" { network_view = "nondefault_netview" cidr = filters = {
network = "192.168.128.0/20"
network_view = "nondefault_netview"
}
// This is just to ensure that the network has been be created // using 'infoblox_ipv4_network' resource block before the data source will be queried.
depends_on = [infoblox_ipv4_network.net2]}
output "nearbyipv4_network_commentnet1" { value = data.infoblox_ipv4_network.nearby_network.comment}output"nearby_network_ext_attrs
// searching for IPv4 networks by specifying EA'sdata "infoblox_ipv4_network" "ipv4_net_ea" { value =data.infoblox_ipv4_network.nearby_network.ext_attrs
}data "infoblox_ipv4_network" "net1" { cidr = 10.1.0.0/24 network_view = "nondefault_netview" filters = {
"*Site" = "Custom network site" "*Site!" = "Office network site"
}}
// retrieves matching IPv4 networks with EA, if any
output"net_ea_out" {
value = data.infoblox_ipv4_network.ipv4_net_ea
}