Missing configurations for transport type, options, logging, sagas, etc

[julealgon]

Being able to configure the message mapping is good, but it is very barebones. Will other configurations be supported in the future?

For example, we currently rely on 2 different transport types in our environment (AWS SQS and PostgreSQL) and changing between them requires manual code changes to support both branches, by reading the setting from our config file and then using a switch statement to change the bus configuration.

Similarly, we have other settings stored in configuration that we use in the .Options call, again all done manually.

[mookid8000]

Rebus' configuration is pretty simple in that regard, because it's just code. (and it's always been this way)

I've seen lots of funny ways of mapping XML and/or JSON to configuration builders, but I haven't seen any examples that I thought were elegant.

If you have any ideas on how it could be made so that it would be elegant (preferably short and concise, preferably with little room for errors that cannot be caught before runtime), I'm all ears 🙂