it should be:
- include: rds.yml
--
Brian Coca
--
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 ansible-project+unsubscr...@googlegroups.com.
To post to
the error seems to indicate bad data is being passed to the rds module
--
Brian Coca
--
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
I am not able to figure out which specific vars is bad...
Is there a problem of file locking ???
Because there is a sg_mysql.yml file being called before rds.yml in main.yml
Something like
- include: sg_mysql.yml
- include: rds.yml
sg_mysql.yml is writing the security group id to be used by
I am working on creating an AWS infrastructure based on Ansible.
I have a playbook which creates an RDS instance. When I run the playbook
standalone it executes perfectly creates RDS instance. However when that
playbook is called by another playbook using the
include: rds.yml
It gives
The main playbook has it as
- include: rds.yml
On Feb 26, 2015 8:13 AM, Brian Coca bc...@ansible.com wrote:
it should be:
- include: rds.yml
--
Brian Coca
--
You received this message because you are subscribed to a topic in the
Google Groups Ansible Project group.
To unsubscribe
Try this instead:
vpc_security_groups: {{ sg_mysql.group_id }}
On Thursday, 26 February 2015 17:40:41 UTC+1, Rahul Mehrotra wrote:
I am not able to figure out which specific vars is bad...
Is there a problem of file locking ???
Because there is a sg_mysql.yml file being called before
I am also facing the same issue while creating security group on aws, using
Ansible 1.8.3 version and 1.6, not really sure but this is something wrong at
aws api library ?
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe
