- Can I use mpp/generali-client-bundle in a Laravel application?
- Not directly. It is a Symfony bundle whose Bundle class and DependencyInjection configuration never execute in Laravel, so composer require installs code with no runtime entry point. Use it as a reference for the Generali contract surface, then extract the transport and client layer into a thin Laravel service provider. Do not plan to adopt it as a runtime dependency in a Laravel-first product.
- How do I install mpp/generali-client-bundle?
- Run composer require mpp/generali-client-bundle, then enable the bundle in a Symfony application's config/bundles.php. Laravel's package discovery will not register it, because it ships no Laravel service provider. Check the composer.json PHP and Symfony constraints and whether it depends on a separate underlying client package before installing.
- How do I configure Generali credentials and endpoints?
- In Symfony, configuration goes through the bundle's DependencyInjection Configuration tree, typically as YAML under config/packages. Credentials should come from environment variables or a secret manager rather than committed YAML. The overview says credentials, endpoints and options are configurable, but it does not list exact keys. In Laravel you would mirror this in config/services.php and .env.
- Does mpp/generali-client-bundle support Laravel 10, 11, or 12?
- It does not target Laravel at all; it is a Symfony bundle, so Laravel version support is not applicable. The relevant constraints are the PHP and Symfony versions declared in its composer.json. Laravel's package discovery will not register its services or configuration.
- Is mpp/generali-client-bundle actively maintained and safe for production?
- The available signals, including 0 stars, 0 dependents and a score of 0, suggest an internal Mon Petit Placement artifact with no external consumers. Expect no documented semver discipline, no security response path and unverifiable test coverage. Insurance workflows can fail silently with incorrect DTO mappings, so add validation and reconciliation around any extracted code. Pin a specific commit if you reuse any part of it.
- How do I test Generali API calls without hitting production?
- The bundle is built on PSR-compatible HTTP abstractions, so you can inject a mocked PSR-18 client in tests. Request a Generali sandbox or test tenant early if one is available to you. Write contract tests around DTO hydration and assert monetary amounts explicitly, because mapping bugs may not throw exceptions.
- Is the Generali integration SOAP or REST, and what authentication does it use?
- The provided overview does not state whether transport is SOAP with WSDL/XSD or REST with OpenAPI, nor whether auth uses mTLS, API keys, OAuth or IP allowlisting. Inspect the underlying client package, endpoints and DTOs before estimating effort. Also confirm Generali's versioning, deprecation and certificate rotation policies with the insurer.
- What are the alternatives to this Symfony bundle for a Laravel Generali integration?
- Extract the transport and DTO layer into a Laravel service provider behind an InsuranceGateway interface with methods such as quote, subscribe and getContract. Alternatively, run a small Symfony sidecar that owns the bundle and expose it over HTTP. Use an official Generali SDK if one exists and is supported. Full Symfony adoption only makes sense if your surrounding stack is already Symfony.
- How do I extract the Generali client from this bundle into Laravel?
- First check composer.json for a separate client dependency such as mpp/generali-client, because that package is the real extraction target and the bundle is just wiring. Pull the client, DTO and hydration code, and drop the Bundle class and DI configuration. Wrap it in a Laravel service provider, bind an interface and configure it through config/services.php and environment variables. Keep the domain layer insurer-agnostic so a second carrier can be added later.
- What license is mpp/generali-client-bundle released under, and can I fork it?
- The provided overview does not state a license. Check the composer.json license field and the repository LICENSE file before vendoring or modifying code. If no license is present, treat it as all rights reserved and request written permission from Mon Petit Placement.