If you use the *--skip-tags* flag in an *ansible-playbook* handlers that
are tagged with specific tags are **not** skipped.
Is that by design or is it a bug?
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and
Is it expected for* ansible-playbook* with* --skip-tags* to not skip
handlers tagged properly?
Let me give an example. If you have the following handler:
- name: NGINX reload
service:
name: nginx
state: reloaded
tags: reload
And you run:
ansible-playbook ... --skip-tags reload
Is
Both are the same... Just a different ways to write YAML.
On Monday, February 23, 2015 at 1:55:19 PM UTC+2, Dick Davies wrote:
shouldn't that be :
- name: NGINX reload
service: name=nginx state=reloaded
tags: reload
?
On 23 February 2015 at 11:36, Ivaylo Bratoev
On 23 February 2015 at 13:15, Ivaylo Bratoev ivaylo.brat...@gmail.com
wrote:
Both are the same... Just a different ways to write YAML.
Not exactly, both are equivalen notations that ansible parses, the former
being pure yaml :)
--
You received this message because you are subscribed to the
Handlers ignore tags, they only run when notified and always run when notified
--
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
shouldn't that be :
- name: NGINX reload
service: name=nginx state=reloaded
tags: reload
?
On 23 February 2015 at 11:36, Ivaylo Bratoev ivaylo.brat...@gmail.com wrote:
Is it expected for ansible-playbook with --skip-tags to not skip handlers
tagged properly?
Let me give an example. If
Try taking out the middle curly braces. So like:
{{ 'prefix_' + item.env + '_postfix' | get_something }}
If you are declaring vars with the vars construct, you don't need to
reference vars as a dict, the key/values are directly available.
Let me know if that helps.
On Sunday, February 22,
Here is a detailed description of my original idea:
http://rosstuck.com/multistage-environments-with-ansible/
It seems that the concept was not obvious for others either. But afer a
little digging they come up with the same concept... ;-)
Regards:
Bence
On Thu, Dec 25, 2014 at 5:17 PM, Bence
Hello Ansiblings,
I am currently working on a guest-based Vagrant provisioner for Ansible
(and the consequent refactoring of the legacy host-based Vagrant Ansible
provisioner).
This feature is planned to be introduced in Vagrant 1.8.0 (which has no ETA
yet).
If you are interested by this new
This isn't directly related to this thread but it was discussed earlier so
it was the best place for it.
I created a filter that converts a yaml dict to a powershell hash. I'm
trying to write some tests for it but I'm not sure how to run just my
specific test. The file playbook and vars are
design, handlers ignore tags, they are only conditional on notification.
--
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
Add your new test role to test/integration/test_winrm.yml with a matching
tag, then run:
TEST_FLAGS=-t test_powershell_filter make test_winrm
It may be worthwhile to add to the test_win_script role to make sure your
filter works for passing parameters to a PowerShell script.
Also, from your
I salute the initiative and effort. FWIW, I've been using Vagrant with the
normal Ansible provisioner quite successfully for about a year now. Never
felt the need of having something like ansible_local provisioner. Was
briefly looking at a few arguments behind this and one was going about
Hi Jazzed,
I used your example as a base for triggering ansible through a python
script, however while the output suggest that the connection to the node is
made and the playbook is running, individual steps on the various roles
fail consistently in contrast to running the playbook using the
Say I have a playbook like this:
- name: install apache config
copy: src=httpd.conf dest=/etc/httpd.conf
notify: restart apache
- name: do something that fails
command: false
I ran it without --force-handlers. The first command ran successfully, and
reported a change. The second command
Hi all,
I have a playbook for provisioning some vagrant machines, written following
the roles approach as described the Best Practices in the website
documenation. The first the role goes and installs docker in all VMs, as
part of that it adds the user vagrant to the docker group, so it can
One use-case that you might not have thought of is developers using
Windows, even if the target machine is Linux. I had this problem on a
previous team and had to hack our own provisioning step to use the
shell and run vagrant locally. Windows will probably never be able to
run vagrant. But why
Some replies inline!
On Mon, Feb 23, 2015 at 1:41 PM, jack.martin8...@gmail.com wrote:
From Ansible doc
http://docs.ansible.com/playbooks_roles.html#introduction:
Roles in Ansible build on the idea of include files and combine them to *form
clean, reusable abstractions*
I really want to
Given your example, pretty simple:
with_flattened: user_groups
But that only works to feed a task. The new feature I referred to, is brand
new, I didn't use it yet, but that would roughly translate to
{{ lookup('flattened', user_groups, want_list=True) }}
On 22 February 2015 at 20:49,
Hey Jack,
The entire mission of Ansible is simple IT automation, right? :) Wherever
possible, my preference would be for a single Ansible playbook to handle
the execution of a single high-level goal/user request. If that isn't
the case, then one needs to somehow bundle those externally,
I'll get a PR up soon to address this.
On Sun, Feb 22, 2015 at 6:22 AM, Michael Perzel michaelper...@gmail.com
wrote:
I opened a new issue at
https://github.com/ansible/ansible-modules-extras/issues/276 in the
correct repository.
I took a look at
On Mon, Feb 23, 2015 at 5:17 PM, Timothy Gerla t...@gerla.net wrote:
Some replies inline!
Thanks for all the help! I'll reply inline too.
On Mon, Feb 23, 2015 at 1:41 PM, jack.martin8...@gmail.com wrote:
From Ansible doc
http://docs.ansible.com/playbooks_roles.html#introduction:
Roles
Yes, currently the only way to avoid that is always run with
--force-handlers. I do have on the wishlist to add this to ansible.cfg
so you can set it globally and not specify it.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
you might want to disable control master/persist for this as it does
reuse the ssh connection.
--
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
you indented with_items too much
On Mon, Feb 23, 2015 at 4:42 PM, Chanaka Samarajeewa chan...@jostle.me wrote:
Hello,
Can someone please let me know why I am getting this error message when
using with_items? Error message my task are as follows.
ERROR: Syntax Error while loading YAML
25 matches
Mail list logo
