Hi
This is what I get when I run drush master-export in a scope called 'vagrant':
$conf['master_version'] = 2;
$conf['master_modules'] = array(
'base' => array(
0 => 'devel',
1 => 'feature_site_config',
),
);And this is what I have in my settings.php file:
$conf['master_modules'] = array(
'base' => array(
'feature_site_config',
),
'vagrant' => array(
'devel',
),
'dev' => array(),
'test' => array(),
'ra' => array(),
'prod' => array(),
);
Am I wrong saying that I should expect to get the devel dependency inside the current scope (vagrant) instead of "base"?
Comments
Comment #1
pere orgaComment #2
pere orgaComment #3
pere orgaComment #4
derhasi commentedThis works as designed.
drush master-exportcannot know what part of your active modules shall be part of a separate scope. It is meant to be a scaffolding command, to get you started with the initial setup of Master-driven project. The script does not care about the currently active scope. Currently the command is only designed to work for an empty master config. (For getting your initial structure you would have useddrush master-export --scopes=vagrant,dev,test,ra,prod.)I guess you are expecting, that the diff of the base scope and the current module set will be the configuration for your current set? We could add that as a feature to the master-export command. I changed the title of the issue ;)
Comment #5
pere orgaTo be honest, I don't really need that feature, it's just that I didn't read the documentation and I expected to see this other behaviour
Comment #6
derhasi commentedI'll close that issue, as you don't need the feature ;)