Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Right now, migrate is marked as a "dangerous" task for sites running the hostmaster profile, and are therefore forbidden.
We now have a (rather hackish) way of upgrading hostmaster sites through the provision-hostmaster-migrate command in the backend. We should therefore be able to upgrade the site through the frontend, somehow.
Cloning is still a no go, i think, but we should consider it, especially with #500362: dispatcher locking.
Comment | File | Size | Author |
---|---|---|---|
#6 | allow_upgrade_of-711746-6.patch | 2.9 KB | helmo |
Comments
Comment #1
adrian CreditAttribution: adrian commentedwe can only do this once we have the queue out of hostmaster.
Comment #2
adrian CreditAttribution: adrian commentedComment #3
Steven Jones CreditAttribution: Steven Jones commentedComment #4
clemens.tolboomIf this is done it should be in HEAD
Comment #5
ergonlogicClosed #454312: self-provisionning support as a duplicate of this issue.
Comment #6
helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commentedHere's a first stab at this, currently adding it to hosting_tasks_extra but could be just as well to the hosting module.
It adds a new task type to just the hostmaster site which in the backend triggers the existing hostmaster-migrate code.
TODO:
Comment #7
ergonlogicNeat! So, just to be clear, updating Provision would still be a manual process? FWIW, the more of the back-end code that we move into front-end
drush/
dirs, the fewer updates to Provision will be required.Comment #8
helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commentedYes, updating provision is out of scope here. When installed as Debian package we don't even have write access to those files.
Comment #9
ergonlogicRight, so how do we handle an upgrade where the backend needs an update too? It seems like we could pretty easily get ourselves in pretty serious trouble. Might there be some way, in
hostmaster-migrate
presumably, to flag that the new platform requires an upgrade to Provision, and fails gracefully? Doeshosting.drush.inc
get bootstrapped on a verify of the hostmaster platform? Maybe something like this could work:Comment #10
helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commentedAdding such a version check sounds like a good idea.
I'm not sure that the new platform is bootstrapped early enough...
drush_provision_hostmaster_migrate_validate calls provision-verify on the new platform which calls drush make. So I guess we could add some checking code at the end of that function.
Comment #11
ergonlogicwouldn't be bootstrapped at the platform level. However, maybe we can add the minimum Provision version to
sites/all/drush/drushrc.php
, since that'd make it easy to access. For example, this works:Comment #12
helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions commented#2648450: hosting_queued fails to restart itself seems to have now solved the queued part.