Weave Code
Cloud Core Laravel Package
google/cloud-core
Shared core infrastructure for Google Cloud PHP libraries. Provides common utilities, configuration, retries, transport/auth helpers, and debugging support used across Google Cloud client components. Generally available with stable, backward-compatible releases.
At a glance
Frequently asked questions about Cloud Core
- Can I use google/cloud-core directly in Laravel, or is it only for Google Cloud PHP services?
- This package is designed as a foundational dependency for Google Cloud PHP services, not a standalone library. However, its utilities like `ApiHelperTrait` or `RetryOptions` can be selectively adopted in Laravel services. For example, you can use its retry logic or authentication helpers independently while keeping other components untouched.
- How do I configure google/cloud-core with Laravel’s .env and config files?
- Use Laravel’s `config/google-cloud.php` for centralized settings and `.env` for environment variables. For example, set `GOOGLE_APPLICATION_CREDENTIALS` in `.env` for ADC (Application Default Credentials) or define `project_id` and retry policies in your config file. The package supports dot-syntax (e.g., `client.options.timeout`) for nested configurations.
- Does google/cloud-core support Laravel’s service container for dependency injection?
- Yes, the package integrates seamlessly with Laravel’s service container. You can bind Google Cloud clients as Laravel bindings with lazy initialization. For example, register a `GcsClient` binding in your `AppServiceProvider` using the container’s config values, ensuring clean and reusable client instances.
- What Laravel versions and PHP versions does google/cloud-core support?
- The package supports PHP 8.1+ (up to 8.4) and is compatible with Laravel 9+. It follows semver, so minor/patch updates are backward-compatible. Always pin to a stable version (e.g., `^1.72`) and use `platform-check` in CI to avoid PHP version mismatches.
- How do I handle authentication in Laravel with google/cloud-core? Should I use ADC or service accounts?
- Use Application Default Credentials (ADC) for simplicity, which leverages `GOOGLE_APPLICATION_CREDENTIALS` in `.env` or the metadata server (GCE/GKE). For CI/CD, fall back to explicit service accounts. Avoid hardcoding credentials; instead, use Laravel’s `env()` helper or environment variables for secure credential management.
- Can I integrate google/cloud-core’s retry logic with Laravel’s queue retries?
- Yes, you can compose both retry mechanisms. Google Cloud’s `RetryOptions` provides exponential backoff with jitter, while Laravel’s queue retries handle job-level failures. For long-running operations, use Laravel queues with `google/cloud-core`'s `LongRunning` clients to avoid blocking web requests.
- How do I mock google/cloud-core clients for Laravel testing?
- Use `google/cloud-core`'s mocking utilities like `MockClient` in Laravel’s `tests/Feature` suites. For example, replace a real `StorageClient` with a mock in your test setup to isolate Google Cloud interactions. This works well with Laravel’s testing helpers like `actingAs` or `refreshDatabase`.
- Does google/cloud-core support Google Cloud emulators (e.g., Storage Emulator) in Laravel?
- Yes, you can integrate emulators by configuring the emulator endpoint in `.env` (e.g., `STORAGE_EMULATOR_HOST`). Use Laravel’s `env()` helper to dynamically set the emulator host in your Google Cloud client configuration. This is useful for local development without hitting production costs.
- What are the performance implications of using google/cloud-core in Laravel?
- The package is optimized for performance, but long-running operations (e.g., resumable uploads) should be offloaded to Laravel queues to avoid web request timeouts. Use client caching (e.g., singleton `GcsClient`) to reduce per-request overhead. Profile resumable uploads with Laravel’s queue workers for best results.
- Are there alternatives to google/cloud-core for Google Cloud integration in Laravel?
- For core utilities like authentication, retries, or transport helpers, `google/cloud-core` is the official and most maintained option. Alternatives like custom wrappers or third-party packages may lack stability or compatibility with Google’s APIs. If you need specific Google Cloud services, use dedicated packages like `google/cloud-storage` alongside this core package.
Weaver
How can I help you explore Laravel packages today?