The s3 module has been removed since ansible 2.7

[mkruk-u2]

Running ansistrano s3 steps with ansible <2.7 generates deprecation warning

[DEPRECATION WARNING]: The 's3' module is being renamed 'aws_s3'. This feature 
will be removed in version 2.7. Deprecation warnings can be disabled by setting
 deprecation_warnings=False in ansible.cfg.

After upgrading ansible to latest version, i.e. 2.7 (at the time of writing) ansible fails with an error:

fatal: [1.2.3.4]: FAILED! => {"changed": false, "msg": "This module has been removed.  The module documentation for Ansible-2.6 may contain hints for porting"}

[ricardclau]

Yeah, it is impossible to maintain compatibility from 2.3 to 2.7 :)

We will soon release a 2.4 syntax version with this change included, please allow us some days

[ricardclau]

Moved to aws_s3 module in 6a7a825cc03bf27ab59dd3804ba561dbedb46650

[ricardclau]

Tag 3.0.0 being baked as we speak

[michaelBenin]

Hey so this is broken for me as well and I updated the config to use the latest:

TASK [carlosbuenosvinos.ansistrano-deploy : ANSISTRANO | S3 | Get object from S3] ***********************************************************************
fatal: [xxx]: FAILED! => {"changed": false, "msg": "This module has been removed.  The module documentation for Ansible-2.6 may contain hints for porting"}

Latest ansible and latest ansistrano.deploy

[michaelBenin]

@ricardclau please reopen this. This is broken.

[ricardclau]

you are not running latest ansistrano

carlosbuenosvinos.ansistrano-deploy is the old name, surely not the new one ansistrano.deploy

[michaelBenin]

It definitely was using ansistrano.deploy 3.0 if it wasn't it would've crashed using the aws_s3 instead of s3

I've been using this role for a very long time and my issues are valid.

[michaelBenin]

Oh you know what - there must be a namespace collision there, I will delete the old one. Sorry!