claw-playbook: drush version issues

[Natkeeran]

It seems that claw-playbook gets the latest drush version. The command and syntax changes considerably between drush versions. For instance, this #783 and related issues are caused by this change. Should we fix the drush version for a given duration, and then do a cyclic updates to drush?

[DigitLib]

@Natkeeran what version you get? I have on CentOS 8.1.10

[Natkeeran]

@DigitLib I get drush 9.0

[whikloj]

This makes sense and seems like an easy fix by adding drush_version: x.x.x exactly matching the drush release version we want to the claw-playbook group_vars files.

[DigitLib]

I started an fresh Ubuntu version today and get 8.1.10 version...

[whikloj]

I'm wondering about this PR. @seth-shaw-unlv should we make a PR to "pin" the drush version before we run your PR through?

Regardless I think this is a good idea, even if we aren' noticing differences between systems I think pinning the version would save us from having the ground shift underneath us.

I can open a quick PR to pin drush at 8.1.10.

[seth-shaw-unlv]

I have no preference which drush version we use (I just want it to work). I think pinning it so it doesn't keep moving around makes sense.

[whikloj]

I'm adding this work to this PR (Islandora-Devops/islandora-playbook#52), just running a quick test then I'll update it.

[whikloj]

I am not adding this to the above PR-52. Why? Let me tell you....

By default the geerlingguy.drush role uses drush-launcher which seems to self-update which explains why we seem to get the latest version when using it.

So I am looking at switching to the composer install method which allows us to use the drush_composer_version: variable to restrict the version (using composer constraints which is nice).

The other alternative is the source install, it uses drush_install_source_version:.

I'm not even sure where I saw drush_version: now...maybe I dreamt it.