eightpoints / guzzle-bundle
Integrates Guzzle 6.x, a PHP HTTP Client, into Symfony. Comes with easy and powerful configuration options and optional plugins.
Installs: 9 840 621
Dependents: 59
Suggesters: 4
Security: 0
Stars: 439
Watchers: 8
Forks: 71
Open Issues: 14
Type:symfony-bundle
Requires
- php: >=7.2
- guzzlehttp/guzzle: ^6.5.8|^7.4.5
- guzzlehttp/promises: ^1.5.3|^2.0
- guzzlehttp/psr7: ^1.9.1|^2.5
- psr/log: ~1.0|~2.0|~3.0
- symfony/expression-language: ~5.0|~6.0|~7.0
- symfony/framework-bundle: ~5.0|~6.0|~7.0
- symfony/stopwatch: ~5.0|~6.0|~7.0
Requires (Dev)
- symfony/phpunit-bridge: ~5.0|~6.0|~7.0
- symfony/twig-bundle: ~5.0|~6.0|~7.0
- symfony/var-dumper: ~5.0|~6.0|~7.0
- symfony/yaml: ~5.0|~6.0|~7.0
Suggests
- namshi/cuzzle: Outputs Curl command on profiler's page for debugging purposes
- dev-master
- v8.5.1
- v8.5.0
- v8.4.0
- v8.3.0
- v8.2.0
- v8.1.0
- v8.0.1
- v8.0.0
- v7.x-dev
- v7.6.2
- v7.6.1
- v7.6.0
- v7.5.0
- v7.4.1
- v7.4.0
- v7.3.1
- 7.3.0
- v7.2.1
- v7.2.0
- v7.1.1
- v7.1.0
- v7.0.0
- v6.x-dev
- v6.2.1
- v6.2.0
- v6.1.2
- v6.1.1
- v6.1.0
- v6.0.1
- v6.0.0
- v5.3.0
- v5.2.3
- v5.2.2
- v5.2.1
- v5.2.0
- v5.1.0
- v5.0.3
- v5.0.2
- v5.0.1
- v5.0.0
- v4.6.0
- v4.5.3
- v4.5.2
- v4.5.1
- v4.5.0
- v4.4.1
- v4.4.0
- v4.3.0
- v4.2.1
- v4.2.0
- v4.1.1
- v4.1.0
- v4.0.1
- v4.0.0
- v3.0.1
- v3.0.0
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.0
- v1.0.0
This package is auto-updated.
Last update: 2024-11-20 14:50:39 UTC
README
Prerequisites | Installation | Configuration | Usage | Plugins | Events | Features | Suggestions | Contributing | Learn more | License
EightPoints GuzzleBundle for Symfony
This bundle integrates Guzzle 6.x|7.x into Symfony. Guzzle is a PHP library for building RESTful web service clients.
GuzzleBundle follows semantic versioning. Read more on semver.org.
Prerequisites
- PHP 7.1 or higher
- Symfony 5.x or 6.x or 7.x
Installation
Installing the bundle
To install this bundle, run the command below on the command line and you will get the latest stable version from Packagist.
composer require eightpoints/guzzle-bundle
Note: this bundle has a Symfony Flex Recipe to automatically register and configure this bundle into your symfony application.
If your project does not use Symfony Flex the following needs to be added to config/bundles.php
manually:
<?php return [ // other bundles here EightPoints\Bundle\GuzzleBundle\EightPointsGuzzleBundle::class => ['all' => true], ];
Configuration
Guzzle clients can be configured in config/packages/eight_points_guzzle.yaml
. For projects that use Symfony Flex this file is created
automatically upon installation of this bundle. For projects that don't use Symfony Flex this file should be created manually.
eight_points_guzzle: # (de)activate logging/profiler; default: %kernel.debug% logging: true # configure when a response is considered to be slow (in ms); default 0 (disabled) slow_response_time: 1000 clients: payment: base_url: 'http://api.payment.example' # NOTE: This option marks this Guzzle Client as lazy (https://symfony.com/doc/master/service_container/lazy_services.html) lazy: true # Default `false` # guzzle client options (full description here: https://guzzle.readthedocs.org/en/latest/request-options.html) options: auth: - acme # login - pa55w0rd # password headers: Accept: 'application/json' # Find proper php const, for example CURLOPT_SSLVERSION, remove CURLOPT_ and transform to lower case. # List of curl options: http://php.net/manual/en/function.curl-setopt.php curl: !php/const:CURL_HTTP_VERSION_1_0: 1 timeout: 30 # plugin settings plugin: ~ crm: base_url: 'http://api.crm.tld' options: headers: Accept: 'application/json' # More clients here
Please refer to the Configuration Reference for a complete list of all options.
Usage
Guzzle clients configured through this bundle are available in the Symfony Dependency Injection container under the name
eight_points_guzzle.client.<name of client>
. So for example a client configured in the configuration with name payment
is available
as eight_points_guzzle.client.payment
.
Suppose you have the following controller that requires a Guzzle Client:
<?php namespace App\Controller; use Guzzle\Client; class ExampleController { public function __construct(Client $client) { $this->client = $client; } }
Using manual wiring this controller can be wired as follows:
services: my.example.controller: class: App\Controller\ExampleController arguments: ['@eight_points_guzzle.client.payment']
For projects that use autowiring, please refer to our documentation on autowiring.
Plugins
This bundle allows to register and integrate plugins to extend functionality of guzzle and this bundle.
Installation
In order to install a plugin, find the following lines in src/Kernel.php
:
foreach ($contents as $class => $envs) { if ($envs[$this->environment] ?? $envs['all'] ?? false) { yield new $class(); } }
and replace them with the following:
foreach ($contents as $class => $envs) { if ($envs[$this->environment] ?? $envs['all'] ?? false) { if ($class === \EightPoints\Bundle\GuzzleBundle\EightPointsGuzzleBundle::class) { yield new $class([ new \Gregurco\Bundle\GuzzleBundleOAuth2Plugin\GuzzleBundleOAuth2Plugin(), ]); } else { yield new $class(); } } }
Known and Supported Plugins
- gregurco/GuzzleBundleWssePlugin
- gregurco/GuzzleBundleCachePlugin
- gregurco/GuzzleBundleOAuth2Plugin
- neirda24/GuzzleBundleHeaderForwardPlugin
- neirda24/GuzzleBundleHeaderDisableCachePlugin
- EugenGanshorn/GuzzleBundleRetryPlugin
Events
This bundle dispatches Symfony events right before a client makes a call and right after a client has made a call. There are two types of events dispatched every time; a generic event, that is dispatched regardless of which client is doing the request, and a client specific event, that is dispatched only to listeners specifically subscribed to events from a specific client. These events can be used to intercept requests to a remote system as well as responses from a remote system. In case a generic event listener and a client specific event listener both change a request/response, the changes from the client specific listener override those of the generic listener in case of a collision (both setting the same header for example).
Listening To Events
In order to listen to these events you should create a listener and register that listener in the Symfony services configuration as usual:
services: my_guzzle_listener: class: App\Service\MyGuzzleBundleListener tags: # Listen for generic pre transaction event (will receive events for all clients) - { name: 'kernel.event_listener', event: 'eight_points_guzzle.pre_transaction', method: 'onPreTransaction' } # Listen for client specific pre transaction events (will only receive events for the "payment" client) - { name: 'kernel.event_listener', event: 'eight_points_guzzle.pre_transaction.payment', method: 'onPrePaymentTransaction' } - # Listen for generic post transaction event (will receive events for all clients) - { name: 'kernel.event_listener', event: 'eight_points_guzzle.post_transaction', method: 'onPostTransaction' } # Listen for client specific post transaction events (will only receive events for the "payment" client) - { name: 'kernel.event_listener', event: 'eight_points_guzzle.post_transaction.payment', method: 'onPostPaymentTransaction' }
For more information, read the docs on intercepting requests and responses.
Features
Symfony Debug Toolbar / Profiler
Logging
All requests are logged to Symfony's default logger (@logger
service) with the following (default) format:
[{datetime}] eight_points_guzzle.{log_level}: {method} {uri} {code}
Example:
[2017-12-01 00:00:00] eight_points_guzzle.INFO: GET http://api.domain.tld 200
You can change the message format by overriding the eight_points_guzzle.symfony_log_formatter.pattern
parameter.
For all options please refer to Guzzle's MessageFormatter.
Suggestions
Create aliases for clients
In case your project uses manual wiring it is recommended to create aliases for the clients created with this bundle to get easier service names and also to make it easier to switch to other implementations in the future, might the need arise.
services: crm.client: '@eight_points_guzzle.client.crm'
In case your project uses autowiring this suggestion does not apply.
Contributing
👍 If you would like to contribute to this bundle, please read CONTRIBUTING.md.
Join our Slack channel on Symfony Devs for discussions, questions and more: #8p-guzzlebundle.
🎉 Thanks to all contributors who participated in this project.
Learn more
- Autowiring Clients
- Configuration Reference
- Disable throwing exceptions on HTTP errors (4xx and 5xx responses)
- Environment variables integration
- How to create a single-file plugin
- How to redefine class used for clients
- Intercept request and response
License
This bundle is released under the MIT license.