dcarbone / php-consul-api
PHP client for the Consul HTTP API
Installs: 321 705
Dependents: 10
Suggesters: 0
Security: 0
Stars: 78
Watchers: 8
Forks: 22
Open Issues: 2
Requires
- php: 8.*
- ext-json: *
- dcarbone/gohttp: v0.3.*
- dcarbone/gotime: v0.5.*
- guzzlehttp/guzzle: ^7.4
- guzzlehttp/psr7: ^2.4
Requires (Dev)
- phpunit/phpunit: @stable
- dev-main
- v2.0.0
- v1.1.7
- v1.1.6
- v1.1.5
- v1.1.4
- v1.1.3
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.5
- v1.0.4
- v1.0.3
- v1.0.2
- v1.0.1
- v1.0.0
- 0.6.x-dev
- 0.6.4
- 0.6.3
- 0.6.2.1
- 0.6.2
- 0.6.1.1
- 0.6.1
- 0.6.0
- 0.5.2
- 0.5.1
- 0.5.0
- 0.4.5
- 0.4.4.1
- 0.4.4
- 0.4.3
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.10
- 0.3.9
- 0.3.8
- 0.3.7
- 0.3.6
- 0.3.5
- 0.3.4
- 0.3.3
- 0.3.2
- 0.3.1
- 0.3.0
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.0
- dev-dcarbone/config-entry
This package is auto-updated.
Last update: 2024-10-11 04:43:28 UTC
README
PHP client for the Consul HTTP API
This library is loosely based upon the official GO client.
Version Compatibility
Newer versions of the api lib will probably work in a limited capacity with older versions of Consul, but no guarantee is made and backwards compatibility issues will not be addressed.
Composer
This lib is designed to be used with Composer
Require Entry:
{ "require": { "dcarbone/php-consul-api": "^v2.0" } }
Configuration
First, construct a Config. This class is modeled quite closely after the Config Struct present in the Consul API Subpackage.
Default Configuration
If you have defined some of the Consul Environment Variables on your hosts then it would probably be easiest to simply execute the following:
$config = \DCarbone\PHPConsulAPI\Config::newDefaultConfig();
Advanced Configuration
You may alternatively define values yourself:
$config = new \DCarbone\PHPConsulAPI\Config([ 'HttpClient' => $client, // [required] Client conforming to GuzzleHttp\ClientInterface 'Address' => 'address of server', // [required] 'Scheme' => 'http or https', // [optional] defaults to "http" 'Datacenter' => 'name of datacenter', // [optional] 'HttpAuth' => 'user:pass', // [optional] 'WaitTime' => '0s', // [optional] amount of time to wait on certain blockable endpoints. go time duration string format. 'Token' => 'auth token', // [optional] default auth token to use 'TokenFile' => 'file with auth token', // [optional] file containing auth token string 'InsecureSkipVerify' => false, // [optional] if set to true, ignores all SSL validation 'CAFile' => '', // [optional] path to ca cert file, see http://docs.guzzlephp.org/en/latest/request-options.html#verify 'CertFile' => '', // [optional] path to client public key. if set, requires KeyFile also be set 'KeyFile' => '', // [optional] path to client private key. if set, requires CertFile also be set 'JSONEncodeOpts'=> 0, // [optional] php json encode opt value to use when serializing requests ]);
Configuration Note:
By default, this client will attempt to locate a series of environment variables to describe much of the above configuration properties. See here for that list, and see here for a list of the env var names.
For more advanced client configuration, such as proxy configuration, you must construct your own GuzzleHttp client prior to constructing a PHPConsulAPI Config object.
As an example:
$proxyClient = new \GuzzleHttp\Client(['proxy' => 'whatever proxy you want']]); $config = new \DCarbone\PHPConsulAPI\Config([ 'HttpClient' => $proxyClient, 'Address' => 'address of server', ]);
When constructing your client, if you are using the GuzzleHttp\Client
object directly or derivative thereof, you may
pass any option listed in the Guzzle Request Options.
Consul
Next, construct a Consul object:
$consul = new \DCarbone\PHPConsulAPI\Consul($config);
NOTE: If you do not create your own config object, Consul will create it's own using Config::newDefaultConfig() and attempt to locate a suitable HTTP Client.
Once constructed, you interact with each Consul API via it's corresponding Client class:
$kvResp = $consul->KV->Keys(); if (null !== $kvResp->Err) { die($kvResp->Err); } var_dump($kvResp->Value);
...as an example.
Current Clients
More will be added as time goes on!
Tests
The testing suite is still in it's infancy, however it is being tested directly against an actual Consul agent. They will be back-filled as time allows. Future plans are to set up a simple cluster to provide a more real-world testing scenario.