Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Currently, platform verify handles platform installation, as well as verification. This should perhaps be broken into separate tasks.
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedThis *must* be split in separate tasks, because we are now using drush make to actually install platform instead of just importing existing ones.
This is especially important for proper rollback procedures, which are impossible to do in the current scenario, as I found out in #1081536: Platform verify doesn't rollback apache config file.
Comment #2
anarcat CreditAttribution: anarcat commentedComment #3
Robin Millette CreditAttribution: Robin Millette commentedsubbing
Comment #4
Steven Jones CreditAttribution: Steven Jones commentedHow would this split work?
Would the frontend task actually call three separate tasks, provison-save, provision-build (?) and then provision-verify instead of the two currently?
Something still has to call make right? So what would that be?
Comment #5
Steven Jones CreditAttribution: Steven Jones commentedRight I see..we want to catch things like: #1081536: Platform verify doesn't rollback apache config file and roll back before we ever generate the platform config files, and the trick is we need to know when this is a platform that we're verifying for the first time, or one that's been verified before and now doesn't verify.
Comment #6
ergonlogicCross-referencing #1950052: Always add a verify task after site install, as it addresses a comparable install->verify workflow for site creation.
Comment #7
ergonlogicSadly, this should probably wait for Aegir 3.