Thanks for the question, Dean.
Handling errors in Policy as Code happened in two phases, validation and audit.
For validation of your policy, both OPA and Cedar provide tools for linting and validation. There's +1 for Cedar, as they allow you to validate your data entities with the policy code you've created.
For auditing, both OPA and Cedar have nice audit logs out of the box that could help you audit. For more advanced auditing, handling, and just-in-time updates, you could use OPAL github.com/permitio/opal. If you are looking for even better error handling then you can use Permit.io which provides rich error-handling interfaces and alerting mechanism, you can read more on Permit.io's audit logs approach here permit.io/blog/audit-logs
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the question, Dean.
Handling errors in Policy as Code happened in two phases, validation and audit.
For validation of your policy, both OPA and Cedar provide tools for linting and validation. There's +1 for Cedar, as they allow you to validate your data entities with the policy code you've created.
For auditing, both OPA and Cedar have nice audit logs out of the box that could help you audit. For more advanced auditing, handling, and just-in-time updates, you could use OPAL github.com/permitio/opal. If you are looking for even better error handling then you can use Permit.io which provides rich error-handling interfaces and alerting mechanism, you can read more on Permit.io's audit logs approach here permit.io/blog/audit-logs