Initializer config rewrites YML config

[yukas]

I found no explicit mention in documentation about what happens if you use number of initialization methods together, say initializer and yml file.

What happens is settings got merged. This can lead to hard to debug issues, when you have initializer using development settings and yml file for capistrano. What happens is upon deployment you will have:
Fog directory can't be blank, Rackspace username can't be blank, Rackspace api key can't be blank type of errors, because it first loads the YML and then rewrite it in initializer with some wrong or empty values.

I believe making yml file priority higher will solve the issue.

Is this reasonable issue to address or am I just stupid to use both config options?