Currently, platform verify handles platform installation, as well as verification. This should perhaps be broken into separate tasks.

Comments

anarcat’s picture

Version: » 6.x-1.0-rc7

This *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.

anarcat’s picture

Title: Break out platform install/verify tasks » Break out drush make calls in a new platform install task
Robin Millette’s picture

subbing

Steven Jones’s picture

Version: 6.x-1.0-rc7 » 6.x-2.x-dev

How 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?

Steven Jones’s picture

Right 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.

ergonlogic’s picture

Cross-referencing #1950052: Always add a verify task after site install, as it addresses a comparable install->verify workflow for site creation.

ergonlogic’s picture

Version: 6.x-2.x-dev » 7.x-3.x-dev

Sadly, this should probably wait for Aegir 3.