Vaurien Client
This is a client for vaurien. It’s a separate project to avoid getting all the dependencies of vaurien when you just want to control it.
It uses the vaurien’s APIs to change the behaviors on the proxy side.
vaurienctl can be used to list the available behaviors, get the current one, or set it.
Here is a quick demo:
$ vaurienctl list-behaviors delay, error, hang, blackout, dummy $ vaurienctl set-behavior blackout Behavior changed to "blackout" $ vaurienctl get-behavior blackout
Using the marteau extension
vaurienclient can be plugged into the marteau mechanism, as a fixture. The fixture class lives in vaurienclient.ext.marteau.
Here is how you can make it work with a .marteau.yml file:
lookup:
- vaurienclient.ext.marteau
fixtures:
memcache_delay:
class: VaurienFixture
arguments:
server: memcache
behavior: delay
vaurien-proxies:
memcache: http://memcache:0123
There are different sections that can be useful here:
lookup tells marteau to load the fixtures that are available on vaurienclient.ext.marteau.
fixtures is the list of fixtures. you give them the class to Use (here the VaurienFixture class, and some arguments.
And then, the last bit is the list of poxies you want to use.
Metadata
Release files for vaurienclient 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vaurienclient-1.1.tar.gz | 3.6 kB | Without provenance | Details |
Release files / vaurienclient-1.1.tar.gz
| Download URL | vaurienclient-1.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6761de714099ce08ffe3dd68438655db12eb4da417896d374e1f5a09d04ea53
|
|
BLAKE2b-256 checksum How to use checksums |
c44d17f942f07f0b9ff22b0a83bd8ce36f2bc73a43ac4534e39869e12f3c4b75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for vaurienclient 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.