Hi there, I've run into a small problem with the ec2_vpc module.
It *looks* like it should be possible to run the ec2_vpc module without specifying subnets. This useful e.g. when you want to: - (1) first define the subnets, then - (2) set up an instance in one of the subnets, and then - (3) define the VPC's route tables, routing some traffic to the instance from step 2. For step 1, I can use ec2_vpc with subnets but no route_tables; for step 3, I can use ec2_vpc with route_tables but no subnets. Unfortunately, the module breaks if no subnets are specified at this point: https://github.com/ansible/ansible-modules-core/blob/devel/cloud/amazon/ec2_vpc.py#L491 ("TypeError: 'NoneType' object is not iterable"). I would have expected that either this was wrapped in a "if subnets is not None:", or that subnets would be a required argument. Is this a bug or am I holding it wrong? Thanks! -- Niko Felger EyeQuant, VP Product & Technology @eyequant | http://facebook.com/eyequant | +49 30 609 899 79 0 -- Our mailing address is: WhiteMatter Labs GmbH | Reichenberger Str. 124, 10999 Berlin Handelsregister: Amtsgericht Charlottenburg, HRB 162605 B | Geschäftsführer: Fabian Stelzer -- 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/CAAoQO3AHsC8T9GB9iG5H2M1-WrbHPeAEnijKQaX5AOrEznStLg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
