I have been working up some playbooks and roles using the various vpc modules. With ec2_vpc, it is possible to lay out vpc, subnets, and routes pretty much all-in-one, while doing the same with the newer (as of 2.0) ec2_vpc_net module requires chaining things such as vpc_id to the ec2_vpc_subnet, igw, and route modules. I can see that separating the functionality allows for more flexibility. Will the original ec2_vpc continue to be developed, or should all effort go into working with the latter modules?
-- 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/e788a579-8f83-4991-9916-ac8b102c9e15%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
