Grégoire Paris

Here is how it's done for `make` in case you are wondering: https://github.com/greg0ire/git_template/blob/820f947e371ea8025b65490c19ae20306b110425/template/hooks/make/pre-push#L6-L8 https://github.com/greg0ire/git_template/blob/820f947e371ea8025b65490c19ae20306b110425/template/hooks/make/pre-commit#L6-L8

:+1: , would be nice. I'm going on holiday this evening until Sunday, so I won't look at it for the moment though.

Thank you again then! An issue is good, this is a feature request, so an issue, sort of...

@odolbeau I don't mean to contribute a default middleware stack. I want to give you the possibility to define *your* middleware stack once, and reuse it as a basis (meaning...

@odolbeau I'm doing very different jobs, based on the same kind of message => I need several queues consumers, it's the best practice if we believe this article : https://derickbailey.com/2015/09/02/rabbitmq-best-practices-for-designing-exchanges-queues-and-bindings/...

I have a slight preference for the first solution, the second one might be overkill, and is more verbose, although more flexible. What do you think?

> Do you use the same middleware stack for different consumers? To clarify, yes, but the innermost processor (the one I write) is not necessarily the same. I say not...

> If I understand well, you would like to have a new configuration key like default_middleware_stack which will be used by default for all your consumers. Yes, that's the first...

# Solution 3: chain configurator ```yaml swarrot: chain_configurator: default: # can be any string, if not empty, a service instance of # ChainConfigurator will be created (swarrot.processor.chain.default) - configurator: swarrot.process.ack...

@duraki would you like to contribute it?