Weave Code
Extractor Bundle Laravel Package
keboola/extractor-bundle
Symfony bundle providing shared infrastructure for building Keboola extractor components in PHP, including configuration handling, input/output mapping, logging, and common extractor lifecycle helpers.
Keboola Extractor Development Bundle
Frequently asked questions about Extractor Bundle
- What is keboola/extractor-bundle used for?
- It provides shared Symfony infrastructure for building Keboola extractor components in PHP, including configuration parsing, dependency injection, logging, input/output mapping, and common extractor lifecycle helpers. The goal is to avoid reimplementing boilerplate in every new extractor. It is not a client for consuming Keboola data from an application.
- Is keboola/extractor-bundle a Laravel package?
- No. It is a Symfony bundle built around Symfony kernel and bundle registration conventions, not a Laravel package. Laravel has no native bundle registry, so the package does not fit as a normal Laravel dependency. Use it in a standalone Symfony extractor project or separate service.
- How do I install keboola/extractor-bundle with Composer?
- Add the Bitbucket repository as a VCS source in composer.json, then require keboola/extractor-bundle from an appropriate tagged release. You will likely need Bitbucket credentials or an internal mirror because the package is not presented as a normal Packagist dependency. Install it in a standalone Symfony extractor project rather than inside a Laravel application.
- Does keboola/extractor-bundle support Laravel 10 or Laravel 11?
- It does not target Laravel versions; it targets Symfony applications and the Keboola component runtime. Its Symfony and PHP constraints may conflict with current Laravel installs that depend on Symfony 6 or 7. Run a short Composer resolution spike against your exact Laravel version before planning any integration.
- Can I use keboola/extractor-bundle inside a Laravel application?
- Technically you could manually register the bundle's services in a Laravel service provider and construct the extractor from the container, but that imports Symfony DI concerns for little benefit. The recommended pattern is a separate deployable extractor image or service invoked from Laravel through a queued job, HTTP endpoint, or process call. Keep Keboola runtime files, exit codes, and configuration handling outside the Laravel app container.
- What PHP and Symfony versions does keboola/extractor-bundle require?
- There is no universal answer in the package overview; inspect the tagged release's composer.json for the PHP floor and Symfony minor-version constraints. Those constraints are the first compatibility gate for any host application. Verify them against your PHP runtime and Laravel's Symfony dependencies before adoption.
- How do I test a Keboola extractor built with this bundle?
- Unit test your extraction and configuration-parsing logic independently of the bundle's runtime bootstrap. Add an integration test that supplies sample config.json and input/output state files, runs the extractor lifecycle, and asserts logs, exit codes, and output mapping. Run that test in a container that resembles the Keboola job environment.
- Is keboola/extractor-bundle still maintained or should I use keboola/php-component?
- Check commit recency, tagged release constraints, and current Keboola developer documentation before committing to the bundle. Public adoption signals are weak, and Keboola's tooling has evolved with keboola/php-component absorbing much extractor scaffolding. If php-component already provides the lifecycle and configuration support you need, prefer the actively recommended path.
- What are the alternatives for consuming Keboola data from Laravel?
- Use the Keboola Storage API and Job Queue REST APIs directly, or a Keboola client library, if the goal is to trigger jobs or read tables from Laravel. keboola/php-component is the relevant alternative when the goal is authoring extractor scaffolding. This bundle is not a client for consuming Keboola data.
- What production and licensing risks should I check before adopting keboola/extractor-bundle?
- Confirm the license and redistribution terms before vendoring or forking the Bitbucket source, because internal mirroring is likely required. The package has weak public adoption signals, no Packagist presence, and no broad failure corpus, so budget for maintenance and upgrade checks. Keep the extractor as a separate deployable with an independent composer.json so its dependency graph never touches Laravel's.
Weaver
How can I help you explore Laravel packages today?