handler + include

[ProfHase]

Hi,

having the following task in my main.yml in a role (tasks/main.yml):

- name: mytask
  copy:
    src=/source
    dest=/destination
  notify: redeploy

with the following handler ( handlers/main.yml):

- name: redeploy
  include: redeploy.yml

I am getting:

ERROR: change handler (redeploy) is not defined

Is this behaviour intended?

I thought of this as the most concise way to consolidate multiple handler tasks.
(I know, there was already a mail  here with the suggestion to notify other handlers in handler which does not seem semantically appropriate)

[Michael DeHaan]

What's defined in handlers/redeploy.yml?

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/a4a328d3-52a9-4d9d-aaff-dfe270db9ce9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ProfHase]

In the handlers/redeploy.yml there are several tasks:

- name: copy installation files
  copy:
    ...

- name: run install script
  command:
    ...

- name: restart myservice
  service:
    ...

[Michael DeHaan]

Yeah, handlers don't work like that, with a "name" on the include like that.

Each handler must have a name and you must notify the names of the handlers specifically.

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/783af2f9-613b-4bfa-b15e-196623846da3%40googlegroups.com.

[ProfHase]

Would that be a possible feature request?
It seems quite logical to me that (like in my case) a handler could consist of multiple related tasks.

Or do I oversee anything?

[David Karban]

Hi,

you can call more, than one handler:

- name: mytask
  copy:
    src=/source
    dest=/destination
  notify:


    - copy installation files


    - run install script


    - restart myservice



David


--

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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9b9b7a29-5217-472f-aebc-73090b06b0ac%40googlegroups.com.

[ProfHase]

Thanks, that is the way I did it. I just think that logically those three (in my case those are 7) operations are just one handler.
(To explain that: if one file has changed, the whole application needs to be rebuilt)
So none of the 7 handlers will ever be called alone and it would require less copy-paste (as the application needs to be rebuilt on change of multiple files)

[Toshio Kuratomi]

On Tue, Nov 18, 2014 at 4:24 AM, ProfHase <profh...@gmail.com> wrote:
> Thanks, that is the way I did it. I just think that logically those three
> (in my case those are 7) operations are just one handler.
> (To explain that: if one file has changed, the whole application needs to be
> rebuilt)
> So none of the 7 handlers will ever be called alone and it would require
> less copy-paste (as the application needs to be rebuilt on change of
> multiple files)
>

This does make sense logically. However, since it's possible to
invoke all the handler tasks in a fairly straightforward way this
would probably be fairly low priority. Perhaps in the future the v2
refactoring will make it easier for us to look into making this
change. At the moment we're just not in a good position to see this
implemented now.

-Toshio