[BUG] Exported configs differ on Playbook and ISLE.

[rosiel]

Overview

Playbook and ISLE provide external services that Drupal uses, and their locations (from Drupal's perspective) are configured in configuration entities that are part of the starter site. Example:

ISLE: broker is at tcp://activemq:61613 Playbook: broker is at tcp://127.0.0.1:61613

The Starter Site happens to contain values that match the Playbook, and ISLE includes a code that configures Drupal to point to the services at the ISLE locations. This is not a problem.

However when someone on ISLE wishes to make a PR against the Starter Site. When they do a config:export and git diff, the changes include these changed values. This makes it very hard to encourage people to do pull requests.

I have a document outlining what I think are the available options for this. To summarize it, I think we should duly consider:

• making ISLE values the standard instead of Playbook
• letting these values vary commit-to-commit (expect whoever is deploying it to set it up as they want)
• using Drupal's Config Override (suggested by @adam-vessey ) (in the document i highlight how this negatively affects the site admin experience)
• using Drupal's Config Split (mentioned by @bibliophileaxe ) (in the document i highlight how this removes entire YAML files from the starter site's management)
• creating a custom script (Drush or otherwise) to reset the specific set of custom values in a set of exported config

[rosiel]

For current convenience, I wrote a shell script to change ISLE values back to Playbook values. It works on my mac. I don't know how to make it portable, sorry.

[rosiel]

As brought up by @Natkeeran , this is still an issue. I propose that we solve the immediate problem which is:

• The current preference for the Playbook's values poses a barrier to contributing to the Starter Site using in ISLE.
• A goal of the Starter Site's architecture is to remove barriers to contributing to the Starter Site, by making it more simple and transparent and straightforward.
• A lot of the folks doing site configuration and testing are using ISLE because it's simpler than Playbook and/or they've got a cool new Mac computer. (not jealous, I swear).

So I propose this which is not a tech solution, but I prefer it because it keeps things simpler and consistent:

• We change the default values to the ISLE values.
• We leave in the step in ISLE where those values are explicitly set using drush config:set (no change!!).
• We fix the steps in the Playbook where those values are supposed to be being set (some are, some aren't!)
• We offer a shell script (the opposite of the one above) that sets the Playbook values back to ISLE values. Playbook users can contribute, but they'll have an extra step. Not ideal but I'm not sure who else is developing Starter Site on Playbook other than me.