Thanks for the response.
> Adding toggles that change behavior is a pattern I try to avoid
That's why I was more leaning towards a form of catch-all key.
> This would also allow bogus data in, such as key names with typos.
If the role's interface uses a fixed list of keys, and they define the
So I was eager to try out the new role argument validation which is in the
pipeline for 2.11
(https://docs.ansible.com/ansible/devel/user_guide/playbooks_reuse_roles.html#role-argument-validation),
but immediately ran into an issue, and thought it would be good to discuss.
The issue is the
