Opposite information provided in one instruction about consul acl bootstrap

On the page: https://developer.hashicorp.com/consul/tutorials/security/access-control-setup-production
You can see:


it is not clear should I use deny or allow policy?

Until now I followed this instruction: https://github.com/hashicorp/learn-nomad-cluster-setup
Everything work fine. Then I changed for my consul server and consul client `acl.enable` to true. And my nomad server do not register itself with Consul. I enabled DEBUG/TRACE and I do not see any error messages regarding failed connection between consul/nomad servers. I tried to follow ACL bootstrap instruction but found that information is a bit confusing.\

It would be awesome if documentation will have links to articles which describes how to troubleshot nomad/consul connection.

Thank you.

Start with the production ACL setup page and compare the two instructions shown in the issue, then review the linked Nomad cluster setup guidance. Clarify whether the bootstrap policy should use deny or allow and add troubleshooting links for Nomad/Consul registration when ACLs are enabled; done means the documentation gives one consistent procedure.

Written by the indexing model from the issue text.