We got burned by this too.
We use Ansible from a single Jenkins server to manage instances in multiple
EC2 VPCs. We use strict host checking for security and we have a custom
known_hosts file per VPC (we've automated updates to known_hosts on each
deploy).
"Reading the SSH config to pick up
Hi,
I'd like to do something like the following:
- name: Wait for Security Group to be applied
command: "aws rds describe-db-instances --db-instance-identifier {{
target_db_environment }}-mysql-db-{{ current_time }} --output json"
register: db_info
set_fact:
security_group_json:
Thanks for info, Dan.
Glad to see that at least someone is already working on it :), and it
probably will be fixed in ver2.
I'm going to remove the "include_vars" from playbook until Ansible 2.0
arrives!
Thank you!
2015年10月3日土曜日 4時08分08秒 UTC+9 Dan Stillman:
>
> I think that's the issue I
On 10/3/15 10:49 AM, t goto wrote:
Thanks for info, Dan.
Glad to see that at least someone is already working on it :), and it
probably will be fixed in ver2.
Well, unfortunately that's not the case — my point was that, even though
this was acknowledged as a bug in 1.9 that had been fixed in
You have typo here
register: dies
it shoild be:
register: dirs
--
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
As it was described in my previous post ;-), but anyway thanks for the note.
On Saturday, October 3, 2015 at 11:25:08 PM UTC-4, Igor Cicimov wrote:
>
> You have typo here
>
> register: dies
>
> it shoild be:
>
> register: dirs
>
>
--
You received this message because you are subscribed to the
