Is it intentional that I can’t notify a handler with a dynamic name?
==> roles/idmapd/tasks/main.yml <==
The other thing which is odd is that if a handler does not exist, this is not reported as an error until there is an attempt to call it.
changed: [storage9.example.com]
ERROR: change handler (restart iptables) is not defined
This is a pain because a change was made, but the handler not run. This means that after the handler is corrected, the next playbook run won’t trigger it because it things the change has already been made.
I haven’t reported this as a bug because it may be intentional behaviour. The only reason I can see for not checking statically that each ‘notify’ line points to a valid handler is if the notify can be generated dynamically - but it appears it cannot.
“Is it intentional that I can’t notify a handler with a dynamic name?”
Yes.