Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An
exists
function lure users into thinking they can use anot exists()
check, or anot_exists()
function, which is not correct. When we pass a non-exist path as function's parameter, the whole rule check stops with result as undefined. None ofnot exists(non_exist_path) nor
not_exists(non_exist_path)` works as expected.Another classic approach is to check existence is like:
If we'd like to assert that the path is not existed, we might use:
But this rule would return a false result if
input.foo.bar
's type is boolean and the value isfalse
.The correct way to check non-existence is:
In rego,
==
function wouldn't be effected by a non-exist path. For symmetry reasons, we stipulate that in this library, we must check the existence by: