Weave Code
Kbc Manage Api Php Client Laravel Package
keboola/kbc-manage-api-php-client
PHP client for the Keboola Management API. It provides ready-made request and response classes plus convenient methods for managing projects, storage, components, configurations, and jobs, making Keboola automation easier from Laravel or any PHP application.
[Read-only] Keboola Management API PHP Client
Frequently asked questions about Kbc Manage Api Php Client
- Is keboola/kbc-manage-api-php-client a Laravel package?
- No. It is a framework-agnostic PHP client for the Keboola Management API, with no Laravel service provider, config file, facade, or published Laravel integration layer. In Laravel you would add it as a Composer dependency and write a small adapter, typically a service provider that binds a configured client singleton plus a config entry for the Manage API endpoint and master token. That glue is yours to own and test.
- How do I install and configure it in a Laravel application?
- Install it with Composer and pin the version you have reviewed, such as exactly 10.4.0 rather than a caret range. Add configuration for the Manage API base URL and token reference, then bind a pre-configured client in a service provider and keep the raw SDK out of controllers and models. Expose intent-named methods such as provisionProject or rotateMasterToken so vendor types do not leak into domain code. Verify the package's PHP constraint, Guzzle major, and PSR HTTP interfaces against your runtime first.
- What can I do with the Keboola Management API client?
- The client wraps Keboola Connection's Manage API, the control-plane surface used to provision and administer projects, stacks, master tokens, storage, components, configurations, and jobs. It is intended for automation, provisioning, monitoring, and integration scripts rather than end-user application features. Every call is a privileged control-plane operation, so treat it as infrastructure automation.
- Can I call the Keboola Management API from a Laravel controller?
- You should not use a Manage API master token in the user-facing request cycle. The token is high-privilege and can create and destroy projects, so a controller or web path holding it is a design defect. Put mutating calls behind a deliberate boundary such as queue workers or a dedicated provisioning service. Expose only safe, intent-specific application actions to users.
- Which PHP and Laravel versions does this package support?
- The package is framework-agnostic, so it does not declare Laravel version support the way a Laravel package would; your app's Laravel and PHP constraints come from your own runtime. You must check the package's composer.json for its PHP constraint, Guzzle major, and PSR HTTP client interfaces. Do not assume Laravel 10 or 11 compatibility from the package name alone; verify against your installed dependency set.
- What changed in keboola/kbc-manage-api-php-client v10.4.0?
- The v10.4.0 release notes contain no described changes, only a compare link between v10.3.0 and v10.4.0. Semver implies a non-breaking minor release, and the 10.x line suggests the project has absorbed major-version churn already, but no notes means you cannot distinguish a bugfix from a behavioural change in error handling or payload shape. Review the diff before adopting or upgrading.
- Should I use ^10.4 or pin the exact Keboola client version?
- Pin exactly 10.4.0 until you have reviewed the diff and confirmed its behavior. Because the release contents are undocumented and this is a control-plane SDK, an unreviewed minor could change error handling or payload shape in ways that matter. Once you have reviewed and tested an upgrade, move deliberately rather than using an open caret constraint.
- How should I test a Keboola Management API integration in Laravel?
- Use a sandbox or non-production Keboola stack if one is available, and start with read-only list and describe operations before enabling any mutating call. In unit tests, mock the HTTP transport rather than hitting a real control plane. Run the SDK path alongside any existing manual or scripted provisioning first so you can compare results. Confirm who holds the master token and whether provisioning calls have an audit trail.
- What are the main risks of using a Keboola control-plane SDK in Laravel?
- The dominant risk is blast radius: a client bug can misprovision or delete tenant infrastructure, not merely render a bad page. The master token is a high-privilege secret, and the library is vendor-maintained, so release cadence and PHP support follow Keboola's roadmap. Change history can also be opaque, as with v10.4.0's compare-link-only notes. Keep the SDK behind a narrow adapter and avoid leaking vendor types into domain code.
- Do I need a Laravel wrapper or are there alternatives to this package?
- The repository does not provide a Laravel wrapper, so any Laravel integration is your own thin adapter. If you only need one or two Manage API calls, direct HTTP calls through Laravel's HTTP client or Guzzle may be simpler than adopting the full SDK. If you standardize on Keboola automation, the SDK's typed request and response classes can reduce boilerplate. Evaluate based on how many control-plane operations you actually need.
Weaver
How can I help you explore Laravel packages today?