- What is douglasdc3/kong and what does it do?
- douglasdc3/kong is a Laravel integration for the Kong API Gateway Admin API. It provides expressive PHP classes and facades to manage Kong resources such as services, routes, consumers, plugins, certificates, and upstreams. It is intended for control-plane automation and internal tooling, not for handling production request traffic.
- How do I install douglasdc3/kong in a Laravel application?
- Install it with Composer using the package name douglasdc3/kong, then register the service provider and facade through package discovery or manual registration if needed. Publish and configure any package config file that controls the Kong Admin API connection. Because the package is archived, vendor or fork it first and pin an exact version instead of relying on a floating constraint.
- Which Laravel and PHP versions does douglasdc3/kong support?
- The exact Laravel and PHP version constraints must be verified from the package composer.json because the last release was in May 2023. The technical assessment flags supported Laravel and PHP versions as a key open question, so do not assume compatibility with current Laravel releases. Validate against your application's exact versions in a proof of concept before adoption.
- Which Kong versions and editions are supported by douglasdc3/kong?
- The available context does not confirm specific Kong version or edition support. The package targets Kong's Admin API, and compatibility with current Kong releases, workspaces, and enterprise features is unproven. Confirm Admin API response shapes and authentication modes against your Kong environment before writing production automation.
- Does douglasdc3/kong support Kong workspaces, RBAC, consumers, plugins, certificates, and upstreams?
- The package overview lists services, routes, consumers, plugins, certificates, and upstreams as managed resources. Workspace and RBAC support are not confirmed in the provided evaluation and are listed as key questions. Inventory the Kong entities and workspace workflows you need, then verify each operation in a non-production Kong workspace.
- How should I store and rotate Kong Admin API credentials for douglasdc3/kong?
- Keep Admin API credentials out of source control and inject them through Laravel environment variables or a secret manager, following the package config conventions. Rotate credentials on a defined schedule and audit every admin call, because the package is control-plane tooling with privileged access. The technical evaluation recommends secret management, audit logging, and rollback before broad rollout.
- Is douglasdc3/kong still maintained and safe for production?
- No, the repository was archived and the last release was 2023-05-16, with zero dependents and very low adoption. Treat it as vendor-or-fork-first rather than a maintained dependency, and expect to own fixes, security patches, and Kong API compatibility work. It can be used behind an internal adapter for internal tooling, but not as core production traffic infrastructure.
- Can I test douglasdc3/kong against a real Kong instance in CI?
- The available evaluation says test coverage and contract testing against Kong are unproven. For any serious use, add your own tests and a contract test suite that runs against the Kong versions and workspaces you support. Start with read-only operations in one workspace, then add low-risk writes before expanding.
- What are alternatives to douglasdc3/kong for managing Kong from Laravel?
- The safest fallback is direct calls to the Kong Admin API from a small internal adapter or a maintained Kong client library. You can also fork douglasdc3/kong, pin the version, and maintain it internally if its fluent Laravel API saves enough effort. The technical evaluation recommends planning a replacement path from the start.
- How should I handle Kong Admin API rate limits, timeouts, and bulk changes with douglasdc3/kong?
- This package is control-plane tooling, so scaling concerns are Admin API rate limits, timeouts, retries, and concurrency rather than request throughput. Use queued jobs for bulk changes, set strict timeouts, and add idempotency where possible. Avoid high-frequency runtime configuration changes and keep calls behind an internal service interface.