Please sign in to comment.
[security] core: undirectional routing wasn't respected in some cases
When creating a context using Router.method(via=somechild), unidirectional mode was set on the new child correctly, however if the child were to call Router.method(), due to a typing mistake the new child would start without it. This doesn't impact the Ansible extension, as only forked tasks are started directly by children, and they are not responsible for routing messages. Add test so it can't happen again.
- Loading branch information...
Showing with 36 additions and 14 deletions.