
Infoblox Triggers IpAllocationTrigger
CertifiedEnterprise EditionTrigger on IPv4/IPv6 address allocation or release events in Infoblox
Infoblox Triggers IpAllocationTrigger
Trigger on IPv4/IPv6 address allocation or release events in Infoblox
Polls the Infoblox WAPI ipv4address or ipv6address endpoint at a configured interval and fires an execution only when the set of matching addresses changes since the last poll. Each state change (addresses added or removed) produces one execution containing only the delta. Use watchStatus=USED to detect allocated addresses, watchStatus=UNUSED to detect released ones.
type: io.kestra.plugin.ee.infoblox.ipam.trigger.IpAllocationTriggerExamples
Trigger when IP addresses are allocated in a network.
id: infoblox_ip_allocation_trigger
namespace: company.team
tasks:
- id: log_allocation
type: io.kestra.plugin.core.log.Log
message: "IP events: {{ trigger.addedCount }} added, {{ trigger.removedCount }} removed in {{ trigger.network }}"
triggers:
- id: watch_allocations
type: io.kestra.plugin.ee.infoblox.ipam.trigger.IpAllocationTrigger
url: "{{ secret('INFOBLOX_URL') }}"
username: "{{ secret('INFOBLOX_USERNAME') }}"
password: "{{ secret('INFOBLOX_PASSWORD') }}"
network: "10.0.0.0/24"
interval: PT1M
watchStatus: USED
Properties
network *string
Network CIDR
IPv4 or IPv6 network CIDR to watch (for example: 10.0.0.0/24).
password *string
WAPI password
Password for HTTP Basic authentication.
url *string
Infoblox Grid Manager URL
Base URL of the Grid Manager (for example: https://infoblox.example.com).
username *string
WAPI username
Username for HTTP Basic authentication.
allowConcurrent boolean
falseSpecifies whether a trigger is allowed to start a new execution even if a previous run is still in progress.
interval string
PT1MdurationPoll interval
How often to poll the WAPI. Defaults to PT1M.
options
HTTP client configuration
Optional HTTP overrides (TLS, timeouts).
io.kestra.core.http.client.configurations.HttpConfiguration
falseIf true, allow a failed response code (response code >= 400)
List of response code allowed for this request
The authentication to use.
io.kestra.core.http.client.configurations.BasicAuthConfiguration
The password for HTTP basic authentication.
The username for HTTP basic authentication.
io.kestra.core.http.client.configurations.BearerAuthConfiguration
The token for bearer token authentication.
io.kestra.core.http.client.configurations.DigestAuthConfiguration
The password for HTTP Digest authentication.
The username for HTTP Digest authentication.
UTF-8The default charset for the request.
java.nio.charset.Charset
trueWhether to enable TCP Keep-Alive extended socket options (TCP_KEEPIDLE, TCP_KEEPINTERVAL, TCP_KEEPCOUNT).
Set to false when running on Windows workers, as these extended socket options are not supported by the Windows JDK and will cause connection failures.
trueWhether redirects should be followed automatically.
REQUEST_HEADERSREQUEST_BODYRESPONSE_HEADERSRESPONSE_BODYThe enabled log.
The proxy configuration.
io.kestra.core.http.client.configurations.ProxyConfiguration
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECTDIRECTHTTPSOCKSThe type of proxy to use.
The username for proxy authentication.
Retry strategy for HTTP requests.
retry is disabled by default.
Constant retry
Retry with a fixed delay between attempts.
durationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseExponential retry
Retry with exponentially increasing delays between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseRandom retry
Retry with a random delay within a configurable range between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalse[502,503,504]HTTP status codes that should be retried.
Used for idempotent methods (GET, HEAD) without their own entry in retryOnStatusCodesByMethod. Non-idempotent methods are never retried on a status code unless listed in retryOnStatusCodesByMethod. Defaults to 502, 503 and 504 for idempotent methods (GET, HEAD) only.
Per-HTTP-method overrides for which status codes should be retried.
Keys are HTTP methods (e.g. GET, POST). A method with no entry here falls back to retryOnStatusCodes. This lets a caller retry more broadly for safe, read-only methods (for example, every 5xx and a 429 for GET/HEAD) while keeping a narrower list for methods that write, where retrying a request that may have already been processed by the origin risks duplicating the effect. Example: {GET: [429, 500, 502, 503, 504], HEAD: [429, 500, 502, 503, 504]}.
["GET","HEAD"]HTTP methods for which any transport-level failure may be retried.
A transport-level failure is a connection or timeout error rather than an HTTP response (e.g. a read timeout or a connection reset mid-request). For a method listed here, any such failure is retried. Defaults to GET and HEAD HTTP methods.
The SSL request options
io.kestra.core.http.client.configurations.SslOptions
Whether to disable checking of the remote SSL certificate.
Only applies if no trust store is configured. Note: This makes the SSL connection insecure and should only be used for testing. If you are using a self-signed certificate, set up a trust store instead.
The timeout configuration.
io.kestra.core.http.client.configurations.TimeoutConfiguration
The time allowed to establish a connection to the server before failing.
PT5MThe time allowed for a read connection to remain idle before closing it.
stopAfter array
CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTEDList of execution states after which a trigger should be stopped (a.k.a. disabled).
wapiVersion string
v2.12WAPI version
WAPI version used in request paths. Defaults to v2.12.
watchStatus string
USEDAddress status to watch
IP address status to monitor. USED matches allocated addresses, UNUSED matches released addresses. Defaults to USED.
when string
trueA condition that determines whether the trigger should run.
A Pebble expression evaluated at trigger time. The trigger fires only when the expression evaluates to a truthy value (true, a non-empty string, a non-zero number). Use this to gate trigger execution on dynamic runtime values such as execution labels, flow variables, or environment conditions.
Outputs
addedCount integer
Number of added addresses
addedEvents array
Added IP events
Addresses newly matching the filter since the previous poll. Each entry contains _ref, ip_address, network, and status.
network string
Watched network
removedCount integer
Number of removed addresses
removedEvents array
Removed IP events
Addresses that were previously matching but no longer match. Each entry contains _ref.