It seems the following thingies don't behave identically:
These:
Can you show me this in a real-world use case? I can’t imagine “heyo, huzzah” in array forms is that important.
Excerpts from Michael DeHaan's message of 2013-05-02 12:46:58 -0400:
Can you show me this in a real-world use case? I can't imagine "heyo,
huzzah" in array forms is that important.
Haha, fair.
So in my shop we've got a pair of F5 LTMs, so I was working on a module
for pulling nodes out of pools, putting them back in, etc.
Because there's a pair of machines, I wanted to pass the module a list
of hosts so that it could find out which one is currently active before
running commands.
So I've got:
Hi Morgan,
Excerpts from Serge van Ginderachter's message of 2013-05-02 13:30:46 -0400:
As we are using Bip-IP F5's ourselves, I'd be very interested to work with
you on this module.
Did you publish it yet?
No, I only started working on it today.
When I get the bare bones of it built, I'll put it on github and send
you a note.
Any use cases in particular you're thinking of, or ideas for what kind
of arguments the module ought to take?
When I get the bare bones of it built, I'll put it on github and send
you a note.
Great!
Any use cases in particular you're thinking of, or ideas for what kind
of arguments the module ought to take?
Not immediately, as i didn't plan to start wokring on such a module, I
didn't thought it through yet. We do have quite some strict standards to
adhere to, so my use cases could be a bit special. We do tend to have a
very strict naming policy.
The basic things we do for every node (actually node pair, as
*everything$ in our environment had a node -1 and -2):
- create the nodes
- create a monitor
- create the pool enabled with that monitor
- create 2 basic virtual servers
- create a virtual server from another service, to be available to this new
set of servers (every pair of nodes lives in its own non routed vlan)
Most variable things when creating a VS, are, for us:
- name
- destination ip and port
- pool
- source nat vlan
- destination vlan
The rest are often defaults. It might be interesting to define some
templates
How to create virtual servers should be possible with some kind of
template, or default set of parameters.
I look forward to have a look at your first version!
Serge
PS: unrelated, but if you allow me to make a shameless plug: I recently
started this project:
https://github.com/ansible-contrib/ansible-plugins
and try to group various ansible plugins which didn't made it (yet) in core.
So in action lines it doesn’t make sense to request an array anyway.
{{ “,”.join(foo) }}
In the other form, since templates effectively ARE about strings, I don’t think you can really expect refering variables inside variable definitions where they are data structures to magically know what you want them to do.