composer_version not honored when a previous version is installed

[EmilioMoreno]

if you specify a version using "composer_version" variable and composer is not installed previously, everything works ok, but if you want to upgrade/downgrade later on to a different composer version, and composer is already installed (no matter what version), the role finishes without doing anything but composer is not upgraded/downgraded.

As we work on specific versions of composer and upgrade to specific versions and not always to the latest, this role do not allow us to upgrade composer.

[stale]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[stale]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

[versusbassz]

I'm not an experienced ansible developer ofc, but i think this behavior isn't correct. Updating composer phar file via changing the role's var could be very very convenient.

[ngstigator]

I'm not an experienced ansible developer ofc, but i think this behavior isn't correct. Updating composer phar file via changing the role's var could be very very convenient.

if you use the composer_version_branch option you can at least change to version 1 i.e. 1.10.17
e.g. composer_version_branch: '--1'

note that composer_version is ignored, so you will not be able install a specific version.

hope this helps.

[gdubicki]

See also #72 and #77 as they are related.