Page Comparison

This topic explains a sample file containing import parameters and possible values. A sample CSV file is provided in Supported Formats. For detailed information about all supported objects, see Mandatory Parameters, DNS Objects, IPAM/DHCP Objects, and Other objects.

In the following example, we are adding authoritative zones. The following image shows the various parts of the sample CSV file. 

Image Removed

The sample CSV file has the following parts:

1. Header - The list of header fields in the sample CSV file. Specify values for header fields marked as mandatory. The list of header fields is shown in Table 1 - Header-<ObjectName>.
2. Values - Values for the header fields. The values are shown in Table 1 - Header-<ObjectName>.
3. Header-ExtraData - The list of Header-ExtraData fields in the sample CSV file. The list of header fields is shown in Table 1 - Header-<ObjectName>.
4. ExtraData - Values for the Header-ExtraData fields. Values for ExtraData fields are shown in Table 2 - Header-ExtraData-<ObjectName> and ExtraData-<ObjectName>.

The following fields are updated with sample values for adding an Authoritative Zone:

• data.items.spec.authZone.fqdn - The FQDN for the Authoritative Zone. 
• data.items.spec.authZone.view - The DNS view. The Authoritative Zone is created under the DNS view default.
• data.items.metadata.name - This identifies the view. The format is DNS view name, FQDN.

The following fields tell BloxOne how to interpret the data while importing each entry. The sample values for the following fields are shown in Table 1 - Header-<ObjectName>: 

• HEADER-<ObjectName> - in this example, we use authzones.
• data.items.apiVersion - values provided in the table.
• data.items.kind - values provided in the table.
• data.items.mergeOptions.key - the value will always be `key`.
• data.items.mergeOptions.parentKind - values provided in the table.
• data.items.metadata.namespace - specify the namespace as required or leave it as 'default.
• data.items.metadata.resourceVersion
• data.items.metadata.selfLink - in the format `/apis/{api}/{version}/namespaces/{namespace}/{object type}/{view name},{FQDN}`
• data.items.spec.key - in the format DNS view name, FQDN.

The following tables provide sample values for the parameters in the sample CSV file. This table primarily focuses on authzones. For detailed information about all supported objects, see Mandatory Parameters, DNS Objects, IPAM/DHCP Objects, and Other objects.

Table 1 - Header-<ObjectName>

...

HEADER-hagroups

...

`dnsconfig.bulk.infoblox.com/v1`

Other possible values based on the object type:

DNS Config: `dnsconfig.bulk.infoblox.com/v1`
Records: `dnsdata.bulk.infoblox.com/v1`
DHCP/IPAM: `ipamdhcp.bulk.infoblox.com/v1`
TSIG Keys: `keys.bulk.infoblox.com/v1`
Tags: `tagging.bulk.infoblox.com/v1alpha1`
Values: `tagging.bulk.infoblox.com/v1alpha1`

...

`AuthZone`

Other possible values based on the object type:

`AuthZone`
`ForwardZone`
`Server`
`View`
`Record`
`Address`
`FixedAddress`
`OptionCode`
`OptionFilter`
`OptionGroup`
`Range`
`TSIGKey`
`Tag`
`Value`

...

["keys.bulk.infoblox.com/tsigkey","
dnsconfig.bulk.infoblox.com/acl",
"dnsconfig.bulk.infoblox.com/view",
"dnsconfig.bulk.infoblox.com/authnsg",
"dnsconfig.bulk.infoblox.com/forwardnsg"]

Other possible values based on the object type:

For forwardzone:

["dnsconfig.bulk.infoblox.com/view",
"dnsconfig.bulk.infoblox.com/forwardnsg"]

For servers:

["keys.bulk.infoblox.com/tsigkey",
"dnsconfig.bulk.infoblox.com/acl"]

For views:

["keys.bulk.infoblox.com/tsigkey",
"dnsconfig.bulk.infoblox.com/acl",
"ipamdhcp.bulk.infoblox.com/ipspace"]

For records:

["dnsconfig.bulk.infoblox.com/view",
"dnsconfig.bulk.infoblox.com/auth_zone",
"dnsconfig.bulk.infoblox.com/forward_zone"]

For addressblocks:

["ipamdhcp.bulk.infoblox.com/ipspace",
"ipamdhcp.bulk.infoblox.com/optionspace",
"ipamdhcp.bulk.infoblox.com/optioncode",
"ipamdhcp.bulk.infoblox.com/optiongroup",
"ipamdhcp.bulk.infoblox.com/optionfilter",
"ipamdhcp.bulk.infoblox.com/hardwarefilter"]

For address:

["ipamdhcp.bulk.infoblox.com/ipspace",
"ipamdhcp.bulk.infoblox.com/subnet"]

For fixedaddress:

["ipamdhcp.bulk.infoblox.com/ipspace",
"ipamdhcp.bulk.infoblox.com/subnet",
"ipamdhcp.bulk.infoblox.com/optionspace",
"ipamdhcp.bulk.infoblox.com/optioncode",
"ipamdhcp.bulk.infoblox.com/optiongroup"]

...

While adding resource records, a prefix RDATA must be added to the start and end of the rdata component in the format viewname, fqdn, name_in_zone, type, RDATA <rdata> RDATA. For example, dee-view-1,test.,mx2,MX,RDATA{\"preference\":11111,\"exchange\":\"poppy.com\"}RDATA.

...

Table 2 - Header-ExtraData-<ObjectName> and ExtraData-<ObjectName>

After adding the data as specified in the above table, add Header-ExtraData-<ObjectName> and ExtraData-<ObjectName> to the CSV file. You can change authzones to the object type you are importing. For example, if you are importing forward zones, you can modify them to HEADER-ExtraData-forwardzones and ExtraData-forwardzones.

...

`dnsconfig.bulk.infoblox.com/v1/namespace/default/authzones`

Other possible values based on the object type:

...

`AuthZoneList`

Other possible values based on the object type:

`ForwardZoneList`
`ServerList`
`ViewList`
`RecordList`
`AddressBlockList`
`AddressList`
`FixedAddressList`
`IPSpaceList`
`OptionCodeList`
`OptionGroupList`
`OptionSpaceList`
`RangeList`
`ServerList`
`SubnetList`
`TSIGKeyList`
`TagList`
`ValueList`

...

Important information about various properties in the JSON/CSV file:

• string: This will produce the string value of a property. Default encoding and the keywords are omitted by default.
• stringarray: This will join each item in a string array with a (,) (comma) and produce the final value enclosed in quotes.
• expandtags: This will inspect a stringyfied JSON tag value and generate headers for each unique key adding the matching value to the associated cell for each row. There can only be one property with this encoding per schema.
• nios: This will use NIOS encoding for embedded arrays of objects. This will add the value of each object property separated by (/) .  An array of items will be separated by (,)  and the produced items are added in the order that the column names appear in the table.

For detailed information about all supported objects, see the following object types: