Weave Code
Salesforce Client Bundle Laravel Package
localfr/salesforce-client-bundle
Symfony bundle that wires a Salesforce API client into your PHP application, providing ready-made service definitions and configuration so you can authenticate and query Salesforce from your own code with minimal setup.
A Symfony bundle that integrates a Salesforce API client into your application, simplifying configuration and service wiring for Salesforce connectivity. It helps keep Salesforce credentials and client setup centralized while exposing the client through Symfony’s dependency injection container.
- Configurable Salesforce client service
- Symfony DI container integration
- Centralized API credentials/configuration
- Reusable client access across services
- Lightweight bundle setup
Frequently asked questions about Salesforce Client Bundle
- Is localfr/salesforce-client-bundle a Laravel package?
- No. It is a Symfony bundle that expects registration in config/bundles.php and Symfony kernel bundle bootstrapping. Laravel has no bundle registry or auto-discovery for Symfony Bundle subclasses, so installing it will not wire services or configuration automatically. For Laravel, evaluate the underlying framework-agnostic client or build your own service provider.
- How do I install localfr/salesforce-client-bundle in Laravel?
- You generally should not install the bundle directly in Laravel because its Symfony service definitions and config tree will not be loaded by Laravel's container. If you only need Salesforce API access, install the underlying localfr PHP client package and bind it in a Laravel service provider. Treat the bundle's configuration keys as a reference for your own config/salesforce.php.
- What configuration does the Salesforce client bundle expect?
- The bundle exposes a Symfony config tree for Salesforce connection values such as base_uri, client_id, client_secret, username, and password, based on the overview. In Laravel you would translate those keys into config/salesforce.php and read them from environment variables inside config files. Do not call env() outside config if you plan to use config:cache. Verify the exact key names against the repository before implementing.
- Which Laravel versions can use this Salesforce client bundle?
- None can use the bundle natively because Laravel does not boot Symfony bundles. Laravel compatibility depends on the underlying client library's PHP and dependency constraints, not on the bundle. Check the client package's PHP requirement against your Laravel floor and run composer why-not for Symfony and Guzzle conflicts. Pin versions and test in a throwaway branch before adopting.
- Does this package support Salesforce REST, Bulk API, or JWT authentication?
- The overview only says it integrates a Salesforce client and wires services and configuration; it does not document which Salesforce APIs or auth flows are covered. You need to inspect the underlying client library and its README to confirm REST, Bulk 2.0, Composite, Metadata, or Streaming support. For server-to-server enterprise use, confirm whether JWT bearer OAuth is implemented, because username-password OAuth is often not acceptable. Do not assume coverage from the bundle name alone.
- Is localfr/salesforce-client-bundle safe for production?
- The evaluation flags high adoption risk: 0 stars, 0 dependents, 0 downloads, and no visible production evidence outside the author's estate. It also notes no SECURITY.md or advisory history for a package that handles client secrets and OAuth tokens. The MIT license and a January 2025 release make it forkable, but you should vendor or wrap the underlying client and own the security review. For credential handling, prefer a maintained client with a disclosure process.
- What is the underlying Salesforce client package and can I use it without Symfony?
- The bundle wraps a localfr PHP Salesforce API client that is described as framework-agnostic and independently installable. That client is the real dependency to evaluate for Laravel, not the Symfony bundle. Bind it as a singleton in a SalesforceServiceProvider, expose it behind a facade if useful, and map credentials from config/services.php. Confirm the exact Composer package name and version constraints in the repository.
- How do I migrate the Symfony bundle configuration to Laravel?
- Translate the bundle's Symfony config tree into config/salesforce.php, using env() only inside that config file so config:cache works. Convert YAML service definitions into container bindings in a dedicated service provider, and replace any Symfony console commands with Artisan commands. The evaluation estimates this as a few days of mechanical work, not weeks. Keep the bundle as documentation and depend only on the client library.
- Are there tests or a sandbox for this Salesforce client bundle?
- The provided evaluation does not confirm test coverage, and it explicitly asks whether tests run against a mocked HTTP client or a real sandbox org. Before relying on it, inspect the repository for a test suite, CI configuration, and HTTP client mocking. If tests are absent, write contract tests around the client calls you depend on. A Salesforce sandbox org is useful for auth and API smoke tests, but avoid live credentials in CI.
- What are alternatives to using a Symfony bundle in Laravel?
- Use a framework-agnostic Salesforce PHP client and wrap it in a Laravel service provider, or use a maintained Laravel-specific Salesforce package if one meets your API and auth needs. If the localfr client is small, vendoring it gives you control over fixes and security patches. The bundle itself adds Symfony DI and http-kernel components without a Laravel boot path, so it is not a good fit. Evaluate API coverage, JWT support, maintenance, and Guzzle compatibility before choosing.
Weaver
How can I help you explore Laravel packages today?