#89 deleting users fails to delet queues...

[psilva]

create an entry in ~/.config/sarra/default.conf

declare source tsource

run sr_audit --users foreground

(it will create some exchanges and queues.)

remove the same line from default.conf

run sr_audit a second time...
017-09-01 22:59:06,425 [INFO] sr_subscribe declare
2017-09-01 22:59:06,425 [INFO] AMQP broker(localhost) user(tsource) vhost(/)
2017-09-01 22:59:09,432 [ERROR] AMQP Sender cannot connect to: localhost
2017-09-01 22:59:09,433 [ERROR] Type=<class 'oserror'="">, Value=Socket closed
2017-09-01 22:59:09,433 [ERROR] Sleeping 5 seconds ...
2017-09-01 22:59:17,454 [ERROR] AMQP Sender cannot connect to: localhost
2017-09-01 22:59:17,455 [ERROR] Type=<class 'oserror'="">, Value=Socket closed
2017-09-01 22:59:17,455 [ERROR] Sleeping 5 seconds ...
2017-09-01 22:59:25,468 [ERROR] AMQP Sender cannot connect to: localhost
2017-09-01 22:59:25,468 [ERROR] Type=<class 'oserror'="">, Value=Socket closed
2017-09-01 22:59:25,468 [ERROR] Sleeping 5 seconds ...
20</class></class></class>

when invoked by sr_audit, likely all operations should be done via admin account,
not user account.

[michel_grenier]

The errors encountered were normal ... it is not an account issue...

getting rid of a broker user (tsource) and leaving sarra configs that uses it
must generate errors at sr_audit level...

The looping is annoying... it can be prevented (loop on broker connection is
enabled by default to make sure to connect when things get better...)
Will fix it if you require it.

Moreover the permission setting for source and subscribe users in sr_audit at the moment in the trunk are incorrect... the flow test would not work under these settings...

Ex.: subscribe user permission on queue ^q_%s_.*
but subscribe code default queue to q_username.process so dot instead of _

     source user permission on exchange ^xs_%s_.*  but simply 
     xs_username should work too...

     Etc...

[michel_grenier]

sr_audit after users/exchanges/queues setup/cleanup could verify all sarra's configs to
see if any process is not properly configured (bad user or bad permission on exchange/queue)
Perhaps move the config to config.conf.bad prior to the default run of sr setup
that would trigger only good configs to have all exchanges/queues configured/created/bound... correctly ... the remaining configs, turned to bad, would not be executed.