: ebs_single_configuration
Best regards,
Christian
Am Dienstag, 29. März 2016 16:40:46 UTC+2 schrieb Christian Kaps:
>
> I have a role which contains tasks that are executed based on a variable
> set in a playbook. In my case I have a *provisioning* playbook and a
> *configuration* playbook. Both
I have a role which contains tasks that are executed based on a variable
set in a playbook. In my case I have a *provisioning* playbook and a
*configuration* playbook. Both share a role named `ebs_single`. In this
role I've tasks which should be executed only in the *provisioning* step
and
Hi,
I've a similar issue and I would be interested if there exists now a
solution to omit task parameters based on variable definitions. In my
special example I've a role to provision EC2 instances. For some instances
I would like to allocate private IP addresses and for some I wouldn't. Any
Hi,
is there any possibility to get the id of the root EBS volume of a newly
created EC2 instance? I cannot find any documentation about it?
Thanks,
Christian
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group
://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Run_Instance_Idempotency.html
-John
On Tue, Apr 8, 2014 at 1:46 PM, Christian Kaps
kaps.ch...@gmail.comjavascript:
wrote:
I think the wait property on the EC2 module is exactly what I want.
Thanks
Am Dienstag, 8. April 2014 09:13:59 UTC+2
Hi,
in the most Playbooks about EC2 provisioning there exists a task which
executes the pause module to wait for the instance to be available. Now
that the EC2 module supports idempotency it is possible to run a playbook
multiple times to add new features to an already provisioned instance.