[WARNING] drd_action_download [drd_domain/88]: Remote instance does not support DRD

Sounds like Message Warning: include(): Failed opening '/code/web/modules/composer/drd_agent/src/Agent/Action/settings.pantheon.php' is the important message here. I wouldn't be surprised if Pantheon's hosting adds a line include "settings.pantheon.php" somewhere in a settings.php file or similar where they then store other stuff by themselves. And when we collect the environment for the automatic update, we can't know that there is another file that would be included and hence the process fails.

To resolve this, an extra plugin would be required to collect such extra components from the hosting environment. That's why the update framework in DRD is built around plugins, so that everyone can add their own plugins as they are needed in their specific context.

You need to find out, how the Pantheon hosting is constructed and what extra elements are required for your update process to run. Hope that helps?

@jurgenhaas Thanks, adrianm6254 and I have looked into this a bit and continue to have some issues. Can you clarify what information we need clarify or confirm with Pantheon tech support on this one?

In the meantime we will take another look at this.

Well, I don't think asking Pantheon would be helpful at this stage.

If you want to automate your site updates, you need to draw a plan first and then build the tool that can automate that. In DRD, we provide some plugins that work for hosting environments, that don't do anything special with extra files or so. Other hosting environments like e.g. Pantheon may do some stuff which is unknown for the outside world and won't be compatible with the existing plugins in DRD.

The steps for the site update through DRD are clearly separated:

• Storage: here you can configure, where the project of your site is stored. In most cases that will be Git, so that DRD is cloning the project from the given source to do all the required work with the project to be updated.
• Build: in this phase, the site will be build, if necessary. For Drupal 8 and later, this is most likely Composer. This will run composer update and any extra command, if necessary and configured.
• Process: in this phase, any extra processing can be performed. We provide 1 example plugin called "LakeDrops Drupal 8" for sites that are built on top of our own composer template. In this section you can also enable the checkbox to pull the live database from your live site, if you need that database for your update process, e.g. testing.
• Testing: let's ignore for now.
• Deployment: in our own scenarios we keep this empty, because deployment of the updated site is not done by DRD. Instead, the deployment of the update is done by a GitLab pipeline when the updates get pulled to the repository, see below.
• Finishing: no necessarily required, but you can add some steps here yourselves for e.g. cleaning up. What happens in this phase as well, when the storage above was e.g. git based, then the result of the modifications will be committed and pushed to the git repository.

The error in the OP seems to happen when pulling the database from the live site in the step Process. DRD uses its built-in command drush drd:database to download a db dump from the remote site. It may be possible that this doesn't work on Pantheon hosting and if so, you may have to find a different way to download a db dump, if you even need one. I recall that Pantheon provides some tools that allow you to do that. With a bit of programming, you can most likely integrate that into this DRD process.

When it comes to the deployment of your updates, I guess Pantheon will be special again, and you may require some programming too. I guess, when pushing the changes to the site repository, Pantheon doesn't automatically deploy that upstream to the live site. You will have to use their API to get that process triggered.

That's as far as I can go. We're not using Pantheon hosting ourselves, so our knowledge is limited. And offering more support is pretty difficult as we have only very limited time resources available.

Jurgen,

Thank you so much, this will help a great deal. Just what I need to look into this further!

I looked through the documentation and found nothing related to this setup or help text in the core edit form. As we investigate this further, we will help with some documentation.