You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using nested/ref head rules is nice, as it allows incrementally building nested structures. Given a common example like the one below however poses a challenge for metadata:
package policy
decision.allow if {
# ... conditions ...
}
decision.reasons := message if {
# ... conditions ...
}
The natural entrypoint here would be the decision rule/object, but it's currently not possibe to annotate as such, as any metadata block above the rules will be bound to the full path (e.g. decision.allow) and not just decision. It's not possible to create a "standalone" decision rule either, as that would conflict with the other declaration.
Allowing a detached metadata block for these rules would be helpful. We could use the scope attribute as a "free form" value that mus point to a path to a rule in the same package/file.
Using nested/ref head rules is nice, as it allows incrementally building nested structures. Given a common example like the one below however poses a challenge for metadata:
The natural entrypoint here would be the
decision
rule/object, but it's currently not possibe to annotate as such, as any metadata block above the rules will be bound to the full path (e.g.decision.allow
) and not justdecision
. It's not possible to create a "standalone"decision
rule either, as that would conflict with the other declaration.Allowing a detached metadata block for these rules would be helpful. We could use the
scope
attribute as a "free form" value that mus point to a path to a rule in the same package/file.The text was updated successfully, but these errors were encountered: