Since we have core-cli, php-script & sql-cli it makes sense to extend Drush Make beyond the realm of what it can do alone by listing a set of executable scripts that can be run by the Drush makefile. These scripts would allow us to do more complex operations like moving or changing files or setting up version control on a new project etc.
Proposed structure:
execute[scriptname][type] = core-cli
execute[scriptname][location] = scripts/
execute[scriptname][type] = php-script
execute[scriptname][location] = scripts/
execute[scriptname][type] = sql-cli
execute[scriptname][location] = scripts/
Scripts are run in the order listed. Re arranging the order changes execution. If no script type is given it looks for core-cli, php-script, sql-cli and execute whichever one it finds first.
This allows us to do interesting things far beyond patching like moving directories around or using sed/awk on the Drupal codebase. We could interact with repositories to do automated git commits after a build. Basically, anything that drush-make doesn't do well can be handled by this external scripting solution.
This brings us closer to a truly extensible deployment system and opens up worlds of possibilities in how we bring our Drupal projects to life.
Comments
Comment #1
rgiles_monigle commentedComment #2
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to
closed (duplicate).Please ask support questions on Drupal Answers.