Falco rules repositories are expected to be hosted in GitHub, GitLab or Bitbucket repos. When adding your repository to Artifact Hub, the url used must follow the following format:
By default the
master branch is used, but it’s possible to specify a different one from the UI.
Please NOTE that the repository URL used when adding the repository to Artifact Hub must NOT contain the git hosting platform specific parts, like tree/branch, just the path to your packages like it would show in the filesystem.
The path to packages provided can contain one or more packages. Each package version must be on a separate folder. You can have multiple rules files in a single package, or create a package for each rules file, it’s completely up to you. In the same way, you can decide if you want to provide one or multiple versions of your rules packages.
The structure of a repository with multiple packages and versions could look something like this:
$ tree path/to/packages path/to/packages ├── artifacthub-repo.yml ├── package1 │ ├── 1.0.0 │ │ ├── README.md │ │ ├── artifacthub-pkg.yml │ │ ├── more │ │ │ └── file3-rules.yaml │ │ ├── file1-rules.yaml │ │ └── file2-rules.yaml │ └── 2.0.0 │ ├── artifacthub-pkg.yml │ └── file1-rules.yaml └── package2 └── 1.0.0 ├── artifacthub-pkg.yml └── file1-rules.yaml
This structure is flexible, and in some cases it can be greatly simplified. In the case of a single package with a single version available at a time (the publisher doesn’t want to make previous ones available, for example), the structure could look like this:
$ tree path/to/packages path/to/packages ├── artifacthub-repo.yml └── package1 ├── README.md ├── artifacthub-pkg.yml └── file1-rules.yaml
In the previous case, even the
package1 directory could be omitted. The reason is that both packages names and versions are read from the
artifacthub-pkg.yml metadata file, so directories names are not used at all.
Each package version needs an
artifacthub-pkg.yml metadata file. Please see the file spec for more details. Rules files must have the
-rules.yaml suffix. If you want to exclude some paths in your package from the indexing, you can do it using the
ignore field in your package metadata file, which uses
Once you have added your repository, you are all set up. As you add new versions of your rules files or even new rules packages to your git repository, they’ll be automatically indexed and listed in Artifact Hub.
- Rules source GitHub URL: https://github.com/tegioz/cloud-native-security-hub/tree/master/artifact-hub/falco
- Repository URL used in Artifact Hub:
https://github.com/tegioz/cloud-native-security-hub/artifact-hub/falco(please note how the tree/master part is not used)