Re: [ansible-devel] Re: 2.2 Roadmap is Posted for Feedback

On 21 June 2016 at 08:26, Ton Kersten wrote: > I was wondering if it isn't time to define a standard of documenting > playbooks and roles? How about not only documenting, but also having some meta information available that defines input and output variables? (the

Re: [ansible-devel] Use "with_sublelements" with 3,4,5,... elements ?

On 11 May 2016 at 11:21, Clément VALENTIN wrote: > Hi, > > I try to use function "with_subelements" to create a folder tree for MySQL > installation with multiple element in vars, but I can't do this ... > > Exemple : > > *vars.yml :* > > mysqld_instance: >> - name:

Re: [ansible-devel] Re: Use "with_sublelements" with 3,4,5,... elements ?

On 12 May 2016 at 09:32, Clément VALENTIN wrote: > Good job, but I did not really want to change ansible sources :/ ​no need, just drop that plugin in lookup_plugins/ next to your playbooks​ -- You received this message because you are subscribed to the Google Groups

Re: [ansible-devel] Re: I can use some help with a pull request

On 25 January 2017 at 12:53, Pieter Voet wrote: > $ > ​​ > git reset --hard upstream:devel > fatal: Invalid object name 'upstream'. > ​That should be a slash, not a colon: ​ git reset --hard upstream/devel ​ ​Serge​ -- You received this message because you are

[ansible-devel] Request for Comments on ideas for a new Ansible Inventory `2.0'

is svg if you want to chat (I'm in #ansible-devel) and my hours are CET - Central Europe. Kind regards, Serge van Ginderachter -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiv

Re: [ansible-devel] module.exit_json with rc > 0

On 27 March 2017 at 18:39, Peter Oliver wrote: > Is rc a bad name to return if I don't want this behaviour? > ​Yes :)​ That's basically how the module reports a failure. -- You received this message because you are subscribed to the Google Groups "Ansible

Re: [ansible-devel] Request for Comments on ideas for a new Ansible Inventory `2.0'

Brian, all, I always intended to get back on this thread, but it seems I forgot about it. On 17 January 2017 at 17:24, Brian Coca wrote: > As for the variable merging and or scoping to targeted group​, I think it > is already too complex and that adding more on top is going

Re: [ansible-devel] Re: ansible 2.4 api and the all.yml file

Have a look here: http://docs.ansible.com/ansible/latest/meta_module.html meta: refresh_inventory is what you need. On 8 December 2017 at 07:36, Paul Cuzner wrote: > > Some further testing > > If I switch the playbook to one that simple dumps all vars on a host, I >

Re: [ansible-devel] Help setting up a module development environment?

On 25 December 2017 at 21:33, Stephen Nesbitt wrote: > NOOB alert! I'm struggling to setup a module development environment that > includes support for unit tests and which the module development > environment does not occur within the Ansible source tree directly.

Re: [ansible-devel] detachable ansible

> > > > but, the extra steps would reduce ansibles simplicity. ansible is the last > tool where we want more moving parts to break. thought of a couple other > ways to get this detached effect. fair amount that can go wrong with > keys/certs in a remote tmux session. could also make an ephemeral

[ansible-devel] Examples of diverse large and inventories

, managing group_vars files becomes very cumbersome, and impossible to keep a good overview. What are the problems you get, when doing inventory at a larger scale? Thanks! Serge -- Forwarded message -- From: Serge van Ginderachter <se...@vanginderachter.be> Date: 10 March 2018 at

Re: [ansible-devel] using groups_vars in INVENTORY

a couple of things: 1/ your group is called win-mssql but the file is win-mssql_.ini (with an extra underscore) 2/ don't use .ini as an extension, those are supposed to be configuration to dynbamic scripts, and are not parsed by ansible directly 3/ group_vars files must be yaml, not ini On

Re: [ansible-devel] Inventori plugin and vault

Fyi https://github.com/ansible/ansible/issues/57012 Serge van Ginderachter On Tue, 27 Aug 2019, 03:51 Josh R, wrote: > With inventory plugins, the only way I got it to work is to encode the > entire yaml file. It then gets decoded when —vault-Id is passed > > -- > You receiv