I do not think you will not upset anyone by submitting a PR. I know that the Ansible Core team is trying to maintain compatibility with organizations that are using Ansible on older platforms. i say submit the PR and see what the core team says. I know they are trying to push forward with all new AWS modules using Boto3. You can see from this PR https://github.com/ansible/ansible-modules-extras/pull/1846 that I wrote to make ec2_vpc_route_table to be 100% boto3. I suggest that you write some tests with that module, which is exactly what I am in the process of doing right now for that PR and just wait and see :)
On Wed, Aug 31, 2016 at 7:51 PM, Nick Aslanidis <[email protected]> wrote: > Hi, > > I'm currently using a lot of extras and core AWS modules and have written > a few myself. I'm wondering what is the etiquette for getting older modules > using the older API's (API's that are no longer developed or supported) to > using the newer Boto3. > > Obviously new modules should be written using Boto3 but given the fact the > older API is not being updated there needs to be a process to rewrite them. > I'm not sure it's practical support boto, boto2 and boto3 by merging > additional boto3 code either as this will make the modules over complex and > verbose which sort of defeats the purpose of having them. > > An example is the following RDS module. > https://github.com/ansible/ansible-modules-core/blob/ > devel/cloud/amazon/rds.py > > I have rewritten this module using the newer boto3 API because I needed to > use the newer functionality, but I don't want to upset anyone by submitting > it as a new module PR. > https://github.com/naslanidis/ansible-modules-extras/blob/ > updated_rds_boto3_module/cloud/amazon/rds_boto3.py > > So my question is, what is the best way to go about sharing my changes > when a complete rewrite of a module is required like this RDS one. I'm just > interested in thoughts on how to approach situations like this. > > Thanks. > Nick. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
