RabbitMQ Plugin for the CloeePy Framework
Attaches a RabbitMQ connection to CloeePy application context.
## Installation
`pip install CloeePy-RabbitMQ`
## Configuration
### Configuration Basics
CloeePy-RabbitMQ configuration must be placed under `CloeePy.Plugins.cloeepy_rabbitmq` in your config file.
The parameters are simply the available `Pika.ConnectionParameters` and `Pika.Credentials`.
For more information on possible configurations please see
[Pika's Documentation](https://pika.readthedocs.io/en/0.10.0/intro.html)
```
CloeePy:
...
Plugins:
cloeepy_rabbitmq:
connectionClass: BlockingConnection
connection:
host: localhost
port: 5672
credentials:
username: guest
password: guest
```
### Connection Class
You must specify which of [Pika's Connection Adapters](https://pika.readthedocs.io/en/0.10.0/modules/adapters/index.html#adapters)
you wish to connect with via the `connectionClass` setting. Options are `BlockingConnection` and `SelectConnection`.
### Customize Plugin Namespace
By default, your connection is available on the CloeePy application context as
`app.rabbitmq`. Optionally you can specify a different namespace by which you access
the rabbitmq connection via `pluginNamespace`.
```
...
Plugins:
cloeepy_rabbitmq:
pluginNamespace: customRabbitMQNS
connectionClass: BlockingConnection
connection:
host: localhost
port: 5672
credentials:
username: guest
password: guest
```
Then, you would access your Redis connection on the application context like so:
```
app = CloeePy()
result = app.customRabbitMQNS.ping()
app.log.info(result)
```
### Optional Environment Variables
It's best practice NOT to store sensitive data, such as database usernames and passwords,
in plain-text configuration files. Thus, CloeePy-RabbitMQ supports configuring your
password via environment variable.
You need to set the following:
- Username: `CLOEEPY_RABBITMQ_USERNAME`
- Password: `CLOEEPY_RABBITMQ_PASSWORD`
By doing so, you can omit `username` and `password` in your configuration file.
## Usage
```
import os
from cloeepy import CloeePy
if __name__ == "__main__":
# Required: set config path as environment variable
os.environ["CLOEEPY_CONFIG_PATH"] = "./example-config.yml"
# instantiate application instance
app = CloeePy()
# Check if RabbitMQ Connection is alive
if app.rabbitmq.is_open:
app.log.info("RabbitMQ conection is open")
else:
app.log.error("RabbitMQ connection is not open")
```
Metadata
Release files for CloeePy-RabbitMQ 0.0.0
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 | Actions |
|---|---|---|---|---|
| CloeePy-RabbitMQ-0.0.0.tar.gz | 3.9 kB | Without provenance | Details for CloeePy-RabbitMQ-0.0.0.tar.gz |
Release files / CloeePy-RabbitMQ-0.0.0.tar.gz
| Download URL | CloeePy-RabbitMQ-0.0.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bafd56c9bf3ef3686c86f6938287a5c7e15ffc10f0e73d10d87af10d82a9480
|
|
BLAKE2b-256 checksum How to use checksums |
520f9ac80026129bf940d79b9cd84e66b8f8018a949bd39e9cc8bef328f0b8ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for CloeePy-RabbitMQ 0.0.0
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.