Helper and conf passing confusion

[ipmb]

Since you mentioned in in #43

don't hesitate if you have any suggestions!

I found BakHelper to be difficult to work with. I started to dig into the code, but eventually gave up. I wanted to create a helper script and have it read a config from a different file path, but ran into several stumbling blocks, including:

• Some methods take a conf as a file name, others take a conf with profiles as top-level keys, and others take a conf for an individual profile. This was confusing and some standardization would help.
• Incorrect defaults were set in the helper and then used to override the conf. For example, I wanted to use swift which was in my default profile, but if I didn't specify it directly in BakHelper, it would get set to DEFAULT_DESTINATION.

It's likely that I'm missing something here that would make this all easier, but that was my experience as a first time user.

[tsileo]

I know BakHelper can be confusing, the same for the configuration management.

That's why, as I said previously, I'm working on the next bakthat version and it will bring a lot of changes, and I hope, it'll make it easier to use. I paused my work on bakthat as I work on some packages I created meant to be used in the next bakthat version.

Thanks for you suggestions!! I leave the issue open, I will close it when the configuration management will be rewritten.