`oslo.policy` supports both enforce and authorize. authorize is
stricter because it'll raise an exception if the policy action is
not found in the list of registered rules. This means that attempting
to enforce anything not found in ``armada.common.policies`` will error
out with a 'Policy not registered' message and 403 status code.
This problem manifests itself through such cases: [0]
Please reference the oslo.policy docs on authorize [1] and
enforce [2] to better understand the discrepancy between the
two.
[0] https://review.openstack.org/#/c/610117/1
[1] feac3dcbfe/oslo_policy/policy.py (L960)
[2] feac3dcbfe/oslo_policy/policy.py (L792)
Change-Id: I5b0a28a2b5fb4dff150f13a56013a7a9b694c756
e573cf1ad5