- Does hprotravel/symfony-gcp-rest-bundle work with Laravel?
- No, not as a drop-in package. It is a Symfony bundle that delivers its value through a Bundle class, a DependencyInjection Extension, a Configuration tree, and services.xml auto-wiring, none of which Laravel recognizes. Composer may autoload the classes, but Laravel will silently ignore every service definition. Adopting it in Laravel is a port, not an install.
- How do I install hprotravel/symfony-gcp-rest-bundle in a Laravel application?
- You can add the Bitbucket VCS repository to Composer and install at a pinned commit SHA if you have credentials, but there is no Laravel package discovery or service provider. You must extract the framework-agnostic GCP REST core and rebuild the wiring as your own ServiceProvider with a config/gcp.php file. If the repo is untagged, avoid an unreproducible dev-master constraint.
- Which Google Cloud Platform REST APIs does this bundle actually cover?
- The package description only says it is a client bundle for GCP REST API endpoints, so coverage is likely a narrow slice rather than full google/cloud-* parity. The vendor namespace suggests endpoint choices may reflect hprotravel's internal travel workloads. Inspect the wrapped services and API versions before assuming it fits your use case.
- Is this bundle a good alternative to google/auth for service account tokens?
- Probably not. Service-account JWT signing, scope handling, and token refresh are security-sensitive, and a homegrown path is materially likelier to mishandle key storage or token caching than google/auth. Check whether the bundle depends on google/auth and PSR-18, PSR-3, and PSR-6, or rolls its own signing, HTTP, and caching. For Laravel, google/auth plus the Http facade is usually safer and fully owned.
- Is hprotravel/symfony-gcp-rest-bundle maintained and safe for production?
- Treat it as high risk until proven otherwise. The assessment notes zero stars, zero dependents, no visible issue tracker, no CVE feed, and a single-organization origin on a private Bitbucket URL, which points to a single-maintainer artifact with no evidence of external production use. Pin a commit, review the code, and have a fallback plan before relying on it in production.
- What Symfony and PHP versions does this bundle require?
- The assessment flags symfony/framework-bundle or symfony/http-kernel as the dependency to check in composer.json. If either is a hard requirement, pulling a Symfony kernel into Laravel to reach a REST client is not a trade worth approving. Confirm the declared PHP and Symfony constraints before any integration work begins.
- How should token caching and authentication be handled if I port this bundle to Laravel?
- Map Symfony CacheInterface injection points to a shared PSR-6 store such as Laravel's cache rather than per-process caching. Convert Symfony LoggerInterface and EventDispatcher injection to PSR-3 and Laravel-native equivalents. Prefer google/auth for signing and refresh unless the existing implementation is already PSR-compliant and well tested. Never commit service-account keys into configuration or source control.
- Can I use this bundle without pulling Symfony into my Laravel application?
- Only by extracting the framework-agnostic core. Delete the Bundle class, isolate the GCP REST call shaping and service-account token handling behind an interface you own, and wrap it in a Laravel ServiceProvider. If the core is thin and the bundle glue is most of the code, the port yields little and you are better off writing the client yourself.
- How do I migrate from this Symfony bundle to Laravel's HTTP client or google/cloud-*?
- The cleanest path is not to adopt the bundle at all: use google/cloud-* where available, or google/auth for tokens plus Laravel's Http facade, which is typically 50 to 100 lines of fully owned code. If you must reuse it, vendor the core behind your own interface so swapping to google/cloud-* becomes a one-class change. Map the Symfony Configuration tree to a Laravel config array by hand because there is no automated bridge.
- Is there a license, and can I fork hprotravel/symfony-gcp-rest-bundle for internal use?
- That is a legal blocker to resolve before any code lands. The Bitbucket organizational URL implies a private repository, and an unlicensed or restrictively licensed private repo may not permit forking or internal redistribution. Check for a LICENSE file and confirm CI runners and every engineer can authenticate to the repository, because composer install will fail otherwise.