How to use the Infoblox plugin

Manage Infoblox DDI — IPv4/IPv6 networks, addresses, DHCP ranges, fixed addresses, DNS records, and leases — from Kestra flows via the Infoblox WAPI REST API.

Authentication

All tasks and the trigger require url (the Grid Manager base URL, e.g. https://infoblox.example.com), username, and password (HTTP Basic credentials; password is a secret) — all required. Optionally set wapiVersion (default v2.12) and options for HTTP client configuration, including relaxing TLS verification for appliances with self-signed certificates. Store secrets in secrets and apply connection properties globally with plugin defaults.

Tasks

Tasks are grouped by resource type under ipam.*. A few conventions apply across all of them:

• Object references — Infoblox identifies objects by WAPI _ref strings, not numeric IDs. Run a List (or Get) task to retrieve a _ref, then pass it as ref to Get, Update, and Delete.
• List tasks share one shape: optional filters (a map of WAPI search parameters) and returnFields (replaces the default field set — only the fields you name, plus _ref, are returned), with maxResults (default 1000) and fetchType (FETCH, FETCH_ONE, STORE, or NONE; default FETCH).
• Update tasks require ref plus at least one mutable field, and reject an empty payload.
• DNS record tasks accept an optional ttl; when set, the plugin enables use_ttl automatically.

IPv4 IPAM

• ipam.network — List, Get, Create, Update, Delete. Create requires network (CIDR); optional networkView, comment. Update changes comment.
• ipam.networkview — List, Create, Delete. Create requires name; optional comment.
• ipam.address — List, plus AllocateNextAvailable and Release. AllocateNextAvailable requires networkRef (a network _ref or CIDR; optional networkView); it atomically reserves one address as a RESERVED fixed address and returns its _ref. Pass that to Release (ref) to delete the reservation. Allocation fails if the network is exhausted.
• ipam.fixedaddress — List, Create, Update, Delete. Create requires ipv4addr; optional mac, matchClient, name, networkView, comment. With the WAPI-default matchClient (MAC_ADDRESS), mac is required — set matchClient: RESERVED for a placeholder without a MAC.
• ipam.range — List, Create, Update, Delete. Create requires startAddr and endAddr; optional network, networkView, comment.

IPv6 IPAM

• ipam.ipv6network — List, Create, Update, Delete. Create requires network (CIDR); optional networkView, comment.
• ipam.ipv6address — List, plus AllocateNextAvailable (requires networkRef; optional networkView) and Release (requires ref), with the same reserve-one-address semantics as ipam.address.
• ipam.ipv6fixedaddress — List, Create, Delete. Create requires ipv6addr; optional duid, matchClient, name, comment. With the WAPI-default matchClient (DUID), duid is required — set matchClient: RESERVED for a placeholder without a DUID.
• ipam.ipv6range — List, Create, Delete. Create requires startAddr and endAddr; optional comment.

DNS records

• ipam.dns.arecord — List, Create, Update, Delete. Create requires name (FQDN) and ipv4addr; optional dnsView, ttl, comment.
• ipam.dns.aaaarecord — List, Create, Update, Delete. Create requires name and ipv6addr; optional dnsView, ttl, comment.
• ipam.dns.cnamerecord — List, Create, Update, Delete. Create requires name (alias FQDN) and canonical (target FQDN); optional dnsView, ttl, comment.
• ipam.dns.ptrrecord — List, Create, Update, Delete. Create requires name and ptrdName, plus either ipv4addr or ipv6addr; optional dnsView, ttl, comment.
• ipam.dns.hostrecord — List, Create, Update, Delete. Create requires name and ipv4Addrs (a list of address entries, each with at least ipv4addr); optional dnsView, comment. Update changes comment.

Leases

• ipam.lease — List only (read-only DHCP lease lookup).

Triggers

ipam.trigger.IpAllocationTrigger fires when IP allocation state changes — set network (an IPv4 or IPv6 CIDR; the address family is detected automatically, required). Optionally set watchStatus (USED for allocated addresses, UNUSED for released ones; default USED) and interval (default PT1M). Each poll compares matching addresses against the previous poll (state persisted in the namespace KV store) and fires only on the delta; an empty delta does not fire. Outputs addedEvents, removedEvents, addedCount, removedCount, and network.