This message was deleted.
# opal
s
This message was deleted.
o
Hi @Robert van der Starre πŸ™‚ I think this is what you’re looking for: https://docs.opal.ac/tutorials/track_a_git_repo#policy-bundle-manifest---serving-dependant-policy-modules
r
thanks for the quick response! I thought that the manifest was only used for the order in which the modules are loaded but if I leave a module out of the manifest then they are not loaded at all?
o
Correct πŸ™‚
r
oh nice, thank you for the information πŸ™‚
Hey @Or Weis I created a manifest and i see in the logging of the server that it can read it: `Explicit manifest to be used: ['generic/functions.rego', 'policy/example/url.rego', 'policy/rbac/rbac.rego']`but when i do a request via the client or the server (
/policy
end point) then I still get the rego tests. In the response from the server I see the following manifest:
Copy code
"manifest": [
    "generic/functions.rego",
    "policy/example/url.rego",
    "policy/rbac/rbac.rego",
    "policy/rbac/rbac_test.rego"
  ],
which I find a bit strange because in the .manifest file looks like this:
Copy code
generic/functions.rego
policy/example/url.rego
policy/rbac/rbac.rego
Am i missing something?
o
Hey @Robert van der Starre we have an open PR to enable excluding files from policy, we should have it merged and released in the next few days πŸ™‚
🦜 1
πŸ™ŒπŸ» 1
o
Sorry for misleading there @Robert van der Starre, I thought that PR was merged already
Perhaps in the interim you can use the POLICY dirs feature, and doing the filtering on the client-side subscribing
r
no problem πŸ™‚ i think this is the PR you are referring to right? https://github.com/permitio/opal/pull/372
I will have a look at the policy dirs feature