Ah, thanks for the pointer, I'll do that. On Sunday, 12 March 2017 08:25:43 UTC+1, Kai Stian Olstad wrote: > > On 10. mars 2017 16:25, Matthew Coltman wrote: > > This is my first time attempting to contribute here and I'm mainly after > a > > bit of a sanity check. > > > > This is the issue I'm looking at: > > https://github.com/ansible/ansible/issues/21588 > > > > The module currently uses boto but boto3 is needed to modify volumes. I > > think the best way to handle this would be to just convert the whole > module > > to use boto3. Of course this can break the module for users missing > boto3, > > but this is an easy fix and boto has been deprecated for a some time > now. > > So I know what I'd do but I'm more wondering if this fits in with the > > "Ansible way" of doing things. > > > > If I go with this way then some integration tests also seem like a good > > idea as there are none currently. > > > > I think that's it for now, any help appreciated. Cheers! > > You might want to try the developer list as documented here > https://docs.ansible.com/ansible/community.html#mailing-list-information > > > -- > Kai Stian Olstad >
-- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a646be5c-0e53-4e91-aed1-f05dc87b4a5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
