This message was deleted.

looks like I should use the manifest functionality I guess? just looking into that now

Hi @Trey Lowerison :) The OPAL server will read all policy files in a certain repo. The OPAL client however can decide what directories inside the repo to read from, so you can filter out directories you don't want. The config var (passed to the client as env var) is called:

OPAL_POLICY_SUBSCRIPTION_DIRS

You can also enforce what policy directories is a client allowed to ask for, by encoding it to the client JWT

so if i just omit a file from the manifest it will still be loaded?

yes

hmm ok. my current repo setup is to have test files living as close to the actual policies they're testing e.g.

create.rego

and

test_create.rego

are in the same directory. is there a way to mark certain files as being included or excluded from a certain topic so i can recursively omit test files?

mmm there is no current way to do so yet.

awesome, yeah i'm down to contribute

Cool 🙂 I think you either want to do an include regex or an exclude regex, or both.

gotcha, i'll start with an exclude regex

this is the relevant code: https://github.com/permitio/opal/blob/master/packages/opal-common/opal_common/git/bundle_maker.py#L220

with CommitViewer(commit) as viewer:
            filter = lambda f: self._has_extension(f) and self._is_under_directories(f)
            explicit_manifest = self._get_explicit_manifest(viewer)
            logger.debug(f"Explicit manifest to be used: {explicit_manifest}")

            for source_file in viewer.files(filter):

You can see that the bundle maker serves files from git. And it passes a filter function to the

CommitViewer.files

method. All you need to do is: 1) create another method, similar to

self._has_extension

that filters based on a regex. 2) create another config var for OPAL, similar to

OPAL_OPA_FILE_EXTENSIONS

and pipe it's value all the way to the bundle maker 🙂

sweet sounds good!

@Trey Lowerison very cool 🙂

sounds good! i'm testing it out in the docker image and found some bugs already, mostly just don't know how to plumb the environment variable down to the BundleMaker so working through that rn