Every time a scan is executed, it's counted as one policy check. If a file pattern that represents several files is passed to the test command (i.e. $ datree test <filePattern>) this scan still counts as one policy check execution. The same goes for a Kubernetes config file that contains several configurations.
For example, if you have two Kubernetes configuration files - demo-app.yaml and prod-app.yaml
If those files are scanned with a single execution:
It will be counted as one policy check execution.
If those files are scanned with two executions:
It will be counted as two policy checks executions.
A set of rules that is executed together on one or several Kubernetes configurations. Each policy is running as a separate entity and has its own result.
The concept of controlling distributed policy execution from a centralized location. This concept enables the policy owner to easily control the rules that are evaluated in each run of Datree without creating operation overhead. The centralized policy can be managed by logging into the dashboard.