Updating Dependencies Breaks Install

[mheadd]

Given the current state of this repo, there are a number of dependencies that are out of date, as well as Drupal Core.

Running the following command successfully updated Drupal core to 8.9.0:

./bin/composer require drupal/core:8.9.0 drupal/pathauto:1.8.0 egulias/email-validator:2.0.0 typo3/phar-stream-wrapper:3.1.3

However, when attempting to run docker-compose up after making this change, the bootstrap script throws an error.

web_1       |  [ERROR] Command "config:import", is not a valid command name. 

This is the line in the bootstrap script that causes the error. Not sure why this occurs, as it appears to be related to Drupal console, which is not changed by the update command listed above.

[onelittlebecca]

I think we need to update composer before updating drupal core per drupal docs. I will plan to take a look this week!

[mheadd]

I think I understand more fully what is happening here. When the Drupal core version is upgraded to 8.9+, the bootstrap.sh fails at the config import step. It's confusing because the error suggests that the command is invalid, but this behavior has been observed with Drupal Console before when there is an error that causes an exception to occur.

Something about the contents or structure of the config that is initially imported is causing Drupal Console to choke at this step when running locally. In addition, when pushing to CG, the install script fails completely and after a successful deploy the user is presented with the standard install screen.

This seems to mean that the contents of the imported config, or the bootstrap.sh script need to be modified. Or both.

[mheadd]

This relates to the work for #52.

[onelittlebecca]

Needs to be updated and config strategy needs to be implemented -- most likely using config split or something of that nature; this will be advantageous for us regardless as it allows for different config settings for different environments. Big fan!