The organisation I'm working in has an installation profile for each site. In the profiles/customsiteprofile/* we have a custom theme and modules. The profile namespace is important to us.

We're also successfully running full config import after installation, it's pretty stable (the full content/entity import is way harder). So anyway, while I've known about the config_installer project for a while, we haven't been able to utilise it.

Assuming there is value here for us, it would be nice if we could call config_installer from our profiles. We use composer, which could theoretically put this code in a specific location and then our profiles could call on it or subclass it, or some magic thing. Have you considered this?

Comments

sime created an issue. See original summary.

jmolivas’s picture

@sime You may want to take a look at this issue https://www.drupal.org/node/1356276

alexpott’s picture

Also there is a proposal to move the bulk of the functionality into core - see #2788777: Allow a site-specific profile to be installed from existing config - which is doing exactly what you want. Unfortunately I don't this is acheiveable with the current way install profiles work.

alexpott’s picture

Status: Active » Closed (works as designed)
Related issues: +#2788777: Allow a site-specific profile to be installed from existing config

As stated in #3 this is not going to be possible but #2788777: Allow a site-specific profile to be installed from existing config is exactly what you want.