Based on how

.manifest

files work, each

.manifest

file's paths must be relative to that manifest's own location, and are meant to reference files within that directory tree — either policy/data files or subfolders containing another

.manifest

to be loaded recursively (1) . The documented format states each line should contain a path that is either a policy/data file or a folder containing another

.manifest

, listed in the order you want them loaded into OPA . The sources don't document support for

../

traversal outside a manifest's own directory tree, which lines up with the warning you're seeing — the bundle maker is telling you that

policies/dir1/../library/utils/policy.rego

resolves to a path outside the

dir1

manifest's own directory scope . For your shared

library/utils/policy.rego

, a documented alternative is to point

OPAL_POLICY_REPO_MANIFEST_PATH

at a different manifest location, or rely on the default alphabetical loading order if you omit manifests altogether . Since your case involves module dependencies (

utils.rego

needing to load before

policy.rego

) , the documented pattern is to place the shared/dependency file so its manifest lists it before the dependent file within the same manifest scope — as shown in the example where

utils.rego

appears before

rbac.rego

in a single manifest because

rbac.rego

imports it . If you want to confirm whether cross-directory references are supported at all, or if this is a known limitation, I'd want more detail: 1. Which Workspace / Project / Env are you using 2. The exact OPAL server config/CURL calls you're using to fetch the bundle 3. Your OPAL server version 4. The full server logs around the bundle build (not just the warning lines) That'll help pin down whether this is expected behavior or something worth deeper investigation.

To learn more, see the sources I considered: [[1] Track a Git Repo | OPAL](https://docs.opal.ac/tutorials/track_a_git_repo)

Thanks for the feedback, glad I was helpful.