- Our website: packit.dev
- CONTRIBUTING.md
The following environment variables can be used to configure the consumer:
Set logging level. Set to one of the Python logging
level strings.
Defaults to INFO if not set.
Set this to a non-empty value in order to skip creating Celery tasks in the worker queue. This is intended to be used to debug the consumer without the danger to create noise in the worker queue.
MQTT broker hostname. Defaults to mqtt.stg.centos.org.
Topic the consumer should listen to. Can use MQTT topic wildcards. Defaults to
git.stg.centos.org/#.
Comma separated list of sub-topics to filter for. No filtering is done if not set.
This is really just a hack, at the moment, in order to work around the fact
that git.centos.org has only 2 topic levels. With this variable it's
possible to filter for partial matches of the second level.
For example, setting this to pull-request will make the consumer handle
git.centos.org/pull-request.new
but ignore
git.centos.org/commit.flag.added
Can be a comma separated list for multiple sub-topics, for example, to handle both messages above set:
MQTT_SUBTOPICS="pull-request,commit"
The "right" solution would be to have git.centos.org use proper MQTT topic
levels, where the topics above would
look like:
git.centos.org/pull-request/new
git.centos.org/commit/flag/added
In this case the consumer could be configured to only listen to
git.centos.org/pull-request/#.
Name of the task containing a message from centos messaging sent to Celery.
Defaults to task.steve_jobs.process_message (tasks in Packit Service).
The following environment variables define the broker used in Celery.
When using redis as a broker, these env vars need to be set:
Defaults to "".
Defaults to 6379.
Defaults to 0.