- How do I install ias/infoblox in a Laravel application?
- Add the private GitLab repository to your composer.json repositories block, configure authentication for theias/di/infoblox, then run composer require ias/infoblox. Because the package is hosted on an internal GitLab with no Private Packagist or Satis mirror mentioned, CI and every developer machine need token or SSH access. Pin to a tagged release if one exists, or to a commit SHA until versioning discipline is confirmed.
- Does ias/infoblox support Laravel 10 and Laravel 11?
- The overview advertises Laravel configuration and facade access, but the technical evaluation warns that the Laravel framing may be aspirational and should be verified in the source. Check composer.json for illuminate/support and laravel/framework constraints, and confirm whether a service provider and facade actually ship. If the package only includes a PHP client and Symfony bundle, you can still bind it into Laravel yourself but should not expect native Laravel 10 or 11 support out of the box.
- How do I configure Infoblox WAPI credentials for ias/infoblox?
- The intended pattern is a config/infoblox.php file populated from environment variables, with host, WAPI version, username, and password or certificate settings. The evaluation recommends wrapping credentials in a Laravel service provider and binding an InfobloxClientInterface rather than scattering config calls. Confirm the exact key names in the package source, because the README excerpt does not document them.
- Can ias/infoblox create and update DNS A, CNAME, PTR, and TXT records?
- The package overview explicitly lists DNS record management for A, CNAME, PTR, and TXT records through simple method calls. In practice, verify that your required record types and update semantics are implemented against the WAPI version your Grid runs. For bulk record creation or zone-level operations, test coverage before relying on it for provisioning.
- How does ias/infoblox allocate IP addresses with next_available_ip?
- The overview describes querying and allocating IP addresses across networks and containers, which usually maps to Infoblox WAPI's next_available_ip function. The evaluation flags next_available_ip, paging, _return_as, and bulk operations as the features that decide most provisioning use cases, and notes they are undocumented here. Verify the implementation against a sandbox Grid before using it for automated allocation.
- Is there a Laravel facade and service provider for ias/infoblox?
- The package description claims facade or dependency-injection access, but the technical assessment says to assume no service provider, facade, publishable config, or Laravel test scaffolding until the source proves otherwise. If they are missing, add a small InfobloxServiceProvider that binds a client singleton and reads credentials from config. That wrapper is modest effort and keeps your application testable.
- Which Infoblox WAPI versions and NIOS releases does ias/infoblox support?
- The provided documentation does not state which WAPI version path, such as /wapi/v2.x/, or which NIOS releases are tested. Infoblox behavior changes materially across WAPI and NIOS versions, so confirm the assumed version in code and test against your Grid. Treat any unlisted version as unsupported until you verify it.
- How can I test ias/infoblox without a production Infoblox Grid?
- The assessment notes no evidence of Laravel test scaffolding and asks whether tests are mocked HTTP unit tests or integration tests against a sandbox Grid. Start with mocked PSR-18 or Guzzle responses for your domain services, then run a small set of integration checks against a non-production Grid if one is available. Because the package has no community issue history, budget time to write your own contract tests.
- What authentication methods does ias/infoblox support for Infoblox WAPI?
- Infoblox WAPI commonly supports basic authentication and certificate-based authentication, and production grids may require Grid Master or HA-pair failover handling. The package overview mentions configurable credentials but does not document which auth modes are implemented. Security review should confirm credential storage and whether certificate auth and HA failover are supported before production use.
- Is ias/infoblox production-ready, and what are the Laravel alternatives?
- The package is a narrow transport adapter for Infoblox DDI, but it has zero stars, zero dependents, private GitLab hosting, unknown versioning, and no community support signal. For production, consider writing a small 300 to 500 line WAPI client you own, or wrapping this package behind your own InfobloxClientInterface so you can swap it. Verify license and fork rights if upstream maintenance stops.