Ah, here:
https://groups.google.com/forum/#!msg/Ansible-project/WpRblldA2PQ/lYDpFjBXDlsJ
I should have totally added another paragraph on imperative and
declarative :)
On Wed, Nov 27, 2013 at 1:58 PM, Matt Jaynes m...@nanobeep.com wrote:
Been googling around for the idempotent memo you
Excerpts from Matt Jaynes's message of 2013-11-27 13:58:10 -0500:
Been googling around for the idempotent memo you mentioned - anyone have a
link? (or maybe it was a joke and I'm a little clueless?) :)
See, it's clear that this mailing list is not nearly idempotent enough!
It should be obvious
I'd be more than happy to improve the rds module. The question I have is
what's the best approach to take. The problem, as I see it, is that the
rds interface is rather complex, so trying to distill it down for Ansible
has the potential to be rather tricky. There are a number of both
I believe you missed my memo on the world says idempotent too much :)
Can you share what happens when you run it again, showing -v from the
ansible-playbook run?
On Mon, Nov 25, 2013 at 4:07 PM, Chris Shenton ch...@koansys.com wrote:
I can create an AWS EC2 instance with the 'ec2' module
On Mon, Nov 25, 2013 at 3:07 PM, Chris Shenton ch...@koansys.com wrote:
Any suggestions how to check for existence of an RDS and only create if it
doesn't exist?
You probably ought to look into using AWS Cloudformation for AWS resource
creation - Ansible has support for it, and it handles
I'd rather have the RDS module upgraded.
CloudFormation requires writing some messy JSON, where as Ansible is a lot
more friendly when using modules directly.
I agree some others may disagree.
On Mon, Nov 25, 2013 at 4:09 PM, Erik Anderson erike...@gmail.com wrote:
On Mon, Nov 25, 2013 at
On Mon, Nov 25, 2013 at 6:57 PM, Michael DeHaan mich...@ansibleworks.comwrote:
CloudFormation requires writing some messy JSON, where as Ansible is a lot
more friendly when using modules directly.
If all you're doing is creating an RDS instance, then yes, absolutely CFN
isn't ideal.
--
You
