Connects to #965: Add --config-dir option to Drush site-install command.

[geerlingguy]

Relates to Issue #965.

Changes proposed:

• Add --config-dir option to Drush site-install command.
• Empower sites using full CMI exports (either via core CMI or with Config Split) to be installed in CI or other environments (otherwise the install fails on UUID issues).

Note: This should be tested on sites that are currently not using full CMI export/import to make sure nothing is broken in the build in that situation.

[grasmash]

@geerlingguy just FYI, you need to use one of the following keywords to "connect" an issue in GitHub to another:

close
closes
closed
fix
fixes
fixed
resolve
resolves
resolved

E.g., "Fixes #965" rather than "Issue #965"

See https://help.github.com/articles/closing-issues-via-commit-messages/

[geerlingguy]

@grasmash This wouldn't close that issue though... it's just related. E.g. the first little bit that would go a ways towards helping two use cases. So in this case I still hope the PR can get merged, but I don't want it to close #965.

[geerlingguy]

Error is:

Import the listed configuration changes? (y/n): y
Drupal\Core\Config\ConfigImporterException: There were errors        [error]
validating the config synchronization. in
Drupal\Core\Config\ConfigImporter->validate() (line 728 of
/home/travis/build/acquia/blt-project/docroot/core/lib/Drupal/Core/Config/ConfigImporter.php).
The import failed due for the following reasons:                     [error]
This import is empty and if applied would delete all of your
configuration, so has been rejected.

Hmm... so our automated tests would only work if you have at least a tiny bit of config exported.

[grasmash]

@geerlingguy Re:keywords. Fair enough. In that case, let's use Waffle.io's keywords so that issues are visually connected on our Kanban board:

connect to
connects to
connected to
connect
connects
connected

[geerlingguy]

We have a kanban board??

[geerlingguy]

@grasmash - I updated the commit message at least—haven't looked into making Travis happy.

[grasmash]

@geerlingguy:

The import failed due for the following reasons: [error]
This import is empty and if applied would delete all of your
configuration, so has been rejected.

[geerlingguy]

@grasmash - Yeah... not sure how to deal with that—this is necessary after you've done your first config dump, but it doesn't work until that's been done. Chicken and egg issue.

Maybe we can have a flag/if/else thing that can say "enable this in the build" and have it off by default?

[grasmash]

I think this is basically a duplicate of #884

[geerlingguy]

@grasmash - Yeah, basically. It would be nice if we had a flag that you could set to enable this option once the project is up and running—and only if you choose to use full CMI (and not --partial).

[geerlingguy]

That would also allow us to default to the current behavior, which can pass tests here in Travis since there isn't any config to kick off a brand new site/project.

[geerlingguy]

Closing since #1080 got in.