❌ Deploy Preview for lando-pantheon failed. Why did it fail? →

Additional notes here:

I've also tried this by dropping a new project in the drupal10 example directory in this.

Connecting to a pantheon site locally here.

name: test-app
recipe: pantheon
config:
  composer_version: 2
  framework: drupal10
  site: site_name
  id: pantheon_site_id

Are you able to provide a reference for any requirement that Drupal requires the MySQL server to have this configuration?

Refer Drupal's DB server requirements:

• https://www.drupal.org/docs/getting-started/system-requirements/database-server-requirements#s-mysql-mariadb-or-percona-server-recommended
• https://www.drupal.org/docs/getting-started/system-requirements/overview#s-database

Which says

MySQL, MariaDB, or Percona Server (Recommended)

Drupal 10

• MariaDB 10.3.7+
• MySQL/Percona 5.7.8+

Drupal 11

• MariaDB 10.6
• MySQL/Percona 8.0

Required configuration

• InnoDB as the primary storage engine
• The PDO database extension

Note: Drupal itself will generally operate with a default MariaDB/MySQL configuration. A more complex site will likely require configuration changes for the database. You can solve these common configuration issues using this documentation.

My understanding is that Drupal's DB connection should be configured for this, per https://www.drupal.org/docs/getting-started/system-requirements/setting-the-mysql-transaction-isolation-level - but I don't know that a MySQL server configuration is required here.

If the MySQL/MariaDB defaults work, I recommend to stick with them as much as possible. If there's a Pantheon or Drupal requirement for the server configuration, let's document that here was part of the reason for introduction.

Only if we know that Pantheon's DB server configuration matches the configuration here, then making this change to match to the Pantheon plugin makes sense to me.

Hmm, if from 10.1.x Drupal has READ-COMMITTED as the default (#1650930), would this be necessary? Maybe the server config drupal.org docs may be due for an update instead?

https://www.drupal.org/project/drupal/issues/1650930#comment-14580623 (2022) further says that it looks like Pantheon has this setting as READ-COMMITTED - if so then yeah the proposed change seems correct for Pantheon plugin.

This underscores the need to add in a pantheon-default or similar test suite that just runs through all the default config to check for things like this, as we did on Acquia: https://github.com/lando/acquia/tree/main/examples/acquia-default. That would make testing this trivial.

Yeah near as I can tell for an existing site, this server level change would be required to avoid seeing the message on the status page. Not having this would also potentially block a Drupal upgrade when working on this locally. I'm open to other ways to approach this though.

@AaronFeledy did you say you were going to take a look at adding some "defaults" tests around this? Know you mentioned something about it last week but wanted to doublecheck before I looked back at it...

@reynoldsalec Haven't had a chance to dig in yet so feel free to take over.