Currently the playbooks do not work if you want to specify a particular version of ST2.
The problems were:
wrong check on using = or - as separately, as logic was if yum else do ... But newer EL are dnf - and so were using the apt separator
st2_version was used for both st2 and st2web packages. And if specified always had to specify st2_revision. This only works if the same revision exists for both packages, but this isn't necessarily the case e.g. 3.4.0 has 3.4.0-1 for st2, and 3.4.0-3 on st2web
On EL systems then there is no need to specify revisions, if use 3.4.0 it would give the latest version. But on Debian the revision needs to be specified
st2chatops was insatlled differntly with a single st2chatops_version that could be used as with or without revision
Updated the playboosk to use the current revision separate for Debian and EL.
Updated the playbooks to use a consistent approach for revisioning, using st2_version, st2chatops_version and st2web_version. This allows the user to either specify with revision for EL and Debian, or they can omit revision on EL.
Currently the playbooks do not work if you want to specify a particular version of ST2.
The problems were:
These issues were raised in https://github.com/StackStorm/ansible-st2/issues/150 Closes #150
Updated the playboosk to use the current revision separate for Debian and EL. Updated the playbooks to use a consistent approach for revisioning, using st2_version, st2chatops_version and st2web_version. This allows the user to either specify with revision for EL and Debian, or they can omit revision on EL.