Closed slint closed 4 years ago
Command | Comment | ||
---|---|---|---|
Declare | configured queues not running | :white_check_mark: | |
configured queues running | :white_check_mark: | ||
specific queue already running | :white_check_mark: | ||
partial state | :white_check_mark: | ||
Delete | configured queues running | :white_check_mark: | |
configured queues not running | :white_check_mark: | ||
specific queues not running | :white_check_mark: | ||
in partial state | :white_check_mark: | ||
Purge | configured queues running | :white_check_mark: | |
specific queues not running | :x: | amqp.exceptions.NotFound: Queue.purge: (404) NOT_FOUND - no queue 'stats-record-view' in vhost '/' |
|
configured queues not running | :x: | = | |
in partial state | :x: | = |
Closed via #11
To avoid errors like
amqp.exceptions.NotFound: Queue.purge: (404) NOT_FOUND - no queue 'stats-record-view' in vhost '/'
, a--force
could be added (similar toinvenio index init --force
), which would ignore errors.This is especially useful for
setup
scripts, which have to "reset" the environment by cleaning up any existing fixtures.Scenarios to check:
foo
, you have created it (viainvenio queues declare
), and then you add another queuebar
, and you want to create it as well viainvenio queues declare
(of course, still keep thefoo
queue)foo
andbar
, but onlyfoo
is actually created, and then you want to runinvenio queues delete
, and end up with no queues at all