[rabbitmq-discuss] Overriding rabbit_auth_mechanism_plain

Ben Hood 0x6e6562 at gmail.com
Wed Mar 13 12:37:30 GMT 2013


I've been overriding the vanilla rabbit_auth_mechanism_plain with a plugin that implements SASL/PLAIN.

It seems that if I shadow the registry of the rabbit_auth_mechanism_plain with my custom mechanism with the same key, because the plugin loader boots my stuff after the core stuff, my definition overrides the previous definition.

Though this behaviour is cool, I was wondering how stable it would remain over time, and whether this particular boot sequence was just happenstance.

So what I've done is to define a boot step that first unregisters the vanilla rabbit_auth_mechanism_plain. If I add this step as a dependency for a second step that registers my custom mechanism this seems to work well.

But I'm wondering if I'm going about this in the wrong way.

Also, I've added a third boot step to kick off some custom initialization for my plugin - so I was also wondering whether this is idiomatic or not.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130313/75f493a0/attachment.htm>

More information about the rabbitmq-discuss mailing list