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
The name of the OCI artifact to package the rules file and the name of the .yaml containing the rules are not the same (- vs _).
See:
OCI
File
falco-rules
falco_rules
falco-incubating-rules
falco-incubating_rules
falco-sandbox-rules
falco-sandbox_rules
Aside, to install and load the rules, the end users need to know their exact names, it leads to a this kind of values.yaml for the official Helm chart:
Without a knowledge about that behavior, we tend to use the same name between the refs for falcoctl and and the list of rules to load.
Feature
The names of the files and OCI artifacts should be the same. Especially, because it would allow to prepare the Helm template to automatically add to the rules_file the downloaded rules. It's a better UX.
Alternatives
Additional context
The text was updated successfully, but these errors were encountered:
I was already aware of this, but I guess this is something we have to solve in bulk with other inconsistencies. Moreover, since just renaming a file is kinda of breaking change, we also may have to bulks such change together and push them to Falco 1.0 eventually.
Motivation
The name of the OCI artifact to package the rules file and the name of the .yaml containing the rules are not the same (
-
vs_
).See:
Aside, to install and load the rules, the end users need to know their exact names, it leads to a this kind of
values.yaml
for the official Helm chart:Without a knowledge about that behavior, we tend to use the same name between the
refs
forfalcoctl
and and the list of rules to load.Feature
The names of the files and OCI artifacts should be the same. Especially, because it would allow to prepare the Helm template to automatically add to the
rules_file
the downloaded rules. It's a better UX.Alternatives
Additional context
The text was updated successfully, but these errors were encountered: