You can stick absolutely everything under args if you want, might make it
feel a bit more consistent.

Also "local_action" is usually not needed in cloud provisioning tasks as
you can just have a play that talks to localhost

- hosts: localhost
  tasks:
   - ec2:
       x: 1
       y: 2
   - ...

etc






On Tue, Jul 22, 2014 at 2:18 PM, Hernandes Sousa <[email protected]>
wrote:

> That was it Brent thanks a lot! You pointed me to the right direction. I
> knew the ec2_tags was an option but I'd like to place the tags in the same
> call. So I followed the same structured as you proposed:
>
> vars:
>     key_name: mykey
>     instance_type: t2.micro
>     security_group: sg-xxxxxxxx
>     image: ami-f5b815e8
>     region: sa-east-1
>     subnet_id: subnet-5eaxxxxb
>     instance_tags:
>       foo: bar
>
> tasks:
>     - name: Launch instance
>       local_action: ec2
>                     key_name={{ key_name }}
>                     group_id={{ security_group }}
>                     instance_type={{ instance_type }}
>                     image={{ image }}
>                     wait=yes
>                     region={{ region }}
>                     assign_public_ip=yes
>                     vpc_subnet_id={{ subnet_id }}
>       args:
>         instance_tags: "{{ instance_tags }}"
>       register: ec2
>
> I will raise a PR adding this example to the documentation may anyone need
> it.
>
> If someone knows of a more elegant way of doing this please let me know.
>
> Thanks
> Hernandes
>
> On Tuesday, July 22, 2014 3:02:42 PM UTC-3, Brent Langston wrote:
>
>> This might be old'ish style at this point, but this is how I do it:
>>
>>     - name: tag my launched instances
>>       local_action: ec2_tag resource={{ item.id }} region={{ region }}
>> state=present
>>       with_items: ec2.instances
>>       args:
>>        tags:
>>         Name: "{{assigned_hostname.stdout}}"
>>         color: "{{oscar_color.stdout}}"
>>         environment: "{{oscar_environment}}"
>>         os: "{{os}}"
>>         owner: "{{owner}}"
>>         phi: "{{phi}}"
>>         pool: "{{pool}}"
>>         primary_role: "{{primary_role}}"
>>         branch: "{{branch}}"
>>
>> Hope that helps.
>>
>> --------
>> Brent
>> --------
>>
>>
>> On Tue, Jul 22, 2014 at 1:53 PM, Hernandes Sousa <[email protected]>
>> wrote:
>>
>>> I'm having trouble setting up instance_tags in the following playbook:
>>>
>>>
>>> vars:
>>>     key_name: mykey
>>>     instance_type: t2.micro
>>>     security_group: sg-xxxxxxxx
>>>     image: ami-f5b815e8
>>>     region: sa-east-1
>>>     subnet_id: subnet-5eaxxxxb
>>>     instance_tags:
>>>       foo: bar
>>>
>>>
>>> tasks:
>>>     - name: Launch instance
>>>       local_action: ec2
>>>                     key_name={{ key_name }}
>>>                     group_id={{ security_group }}
>>>                     instance_type={{ instance_type }}
>>>                     image={{ image }}
>>>                     wait=yes
>>>                     region={{ region }}
>>>                     assign_public_ip=yes
>>>                     vpc_subnet_id={{ subnet_id }}
>>>                     *instance_tags="{{ instance_tags }}" # not working*
>>>       register: ec2
>>>
>>>
>>> I get "msg: this module requires key=value arguments", does anyone know
>>> the correct way to add the dictionary in this case? I've tried a variety of
>>> combinations without much success.
>>>
>>> --
>>> 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/99f1a77f-35f6-4920-b260-
>>> 04ff433f245d%40googlegroups.com
>>> <https://groups.google.com/d/msgid/ansible-project/99f1a77f-35f6-4920-b260-04ff433f245d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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/f987d7b3-221c-4416-949e-01fafb4ce156%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/f987d7b3-221c-4416-949e-01fafb4ce156%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BnsWgxLLnQLN2sg4nCx1Etqe%3DOJKPcxT%2BWY1WWj%3D37tg2akbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to