RFC: Requiring latest stable version of boto for AWS module refactoring/additions

Archives Ansible Developer
1

I’ve been sifting through some of the tickets on GitHub related to AWS modules and feel that some of the pains with maintaining them could be eliminated by making it acceptable to require the latest stable version when refactoring or making AWS modules (maybe even boto3 when it become stable).

My initial logic is that in order to use the AWS modules the Ansible control node will always necessarily have internet connectivity (not to say it isn’t restricted connectivity) to at LEAST AWS API endpoints and PyPi (though it could technically be an private mirror and some users may have installed boto manually). With that, I think it should be very small barrier for an Ansible + AWS user to upgrade boto to the latest stable version when needed.

Any comment/input is appreciated.

Cheers

2

I tend to install most python packages through RPMs these days. On a RHEL/CentOS 7 node, that means anything including EPEL is likely fine. python-boto is available through yum, but python-boto3 isn’t.

It looks like boto3 is only just getting reviewed for Fedora [1] which makes me think that requiring it is premature.

I’m happy with boto3 being used by stuff that just doesn’t exist in old boto, I don’t think that should be a blocker, but let’s not break enterprise systems before we have to.

That being said, we should have a set level of boto and boto3 support - we can afford to get rid of some checks and error messages for versions that are very ancient.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1295129