lpmqtt, like its name implies, is a tool for publish a launchpad event stream into MQTT. It will publish all the capture events from the lp emails over imap and publish them to MQTT
MQTT Topics
lpmqtt will push launchpad events to topics broken by project and event type. The formula used is:
<base topic>/<project>/<bugs, blueprints, or other event type>/<bug number>
However only the base topic is a guaranteed field. Depending on the emails sent by launchpad some of the other fields may not be present. In those cases the topic will start from the base topic and will use fields moving towards the right until one is missing.
Configuration
There are a few required pieces of information to make lpmqtt work properly. These settings are specified in the config file.
IMAP
To configure lpmqtt to listen to your imap server you need to provide 3 pieces of information in the [imap] section
hostname - The hostname for the imap server to connect to
username - The username to connect with
password - The password to use
There are also a number of optional settings you can use depending on the configuration of the imap server you’re connecting to:
use_ssl - Set this to True to establish an imaps connection with ssl
- folder - Specify a mailbox/folder to watch for message from launchpad.
If one is not specified INBOX will be used
- delete-old - Set this to True to have lpmqtt delete messages after it
finishes processing them. By default it will just mark them as read.
MQTT
Just as with imap there are a few required options for talking to MQTT, which is the other axis of communication in lpmqtt. The options for configuring MQTT communication go in the [mqtt] section. The 2 required options are:
hostname - The hostname for the MQTT broker
base_topic - The base topic name to use for the gerrit events
There are also a couple optional settings for communicating with mqtt that you can set:
- port - The port to communicate to the MQTT broker on. By default this
is set to 1883, the default MQTT port. This only needs to be set if your broker uses a non-default port.
- keepalive - Used to set the keepalive time for connections to the MQTT
broker. By default this is set to 60 seconds.
- username - Used to set the auth username to connect to the MQTT broker
with.
- password - Used to set the auth password to connect to the MQTT broker
with. A username must be set for this option to be used.
2 maintainers
Metadata
2 maintainers
Release files for lpmqtt 0.0.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 | |
|---|---|---|---|---|
| lpmqtt-0.0.1.tar.gz | 10.2 kB | Without provenance | Details |
Release files / lpmqtt-0.0.1.tar.gz
| Download URL | lpmqtt-0.0.1.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2bd4005d8f6ab0d080f4a92d4ba2a37876c129da7f01ed651473c2139aa92d3
|
|
BLAKE2b-256 checksum How to use checksums |
0b26247789208bcd658159b552b76cfef6e3616495b3fed6cf5c7659e55186c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lpmqtt 0.0.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.
