@wolf31o2 This attribute naming scheme is tedious by including file names, and inconsistent with the current api.  There isn't a compelling reason to do that, unless you're passing in that scoped hash to be walked/unrolled in the configuration file.  It would probably be better to scope them by recipe or role, so it is consistent and clear to users which attribute affects which recipe.

Could we scope it by role/recipe (default|kdc|kadmin) so that:
* default
  - krb5.conf controlled by default recipe is scoped to `node['krb5']`
* kdc
  - kdc.conf controlled by kdc recipe is scoped to `node['krb5']['kdc']`
* kadmin
  - kadm5.conf controlled by kadmin recipe is scoped to `node['krb5']['kadmin']`