Generate config-relative Gate policy paths#13
Conversation
PR SummaryLow Risk Overview The generated Gate README is updated to call out this portability, and the CLI Reviewed by Cursor Bugbot for commit cf511fa. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.
Reviewed by Cursor Bugbot for commit cf511fa. Configure here.
| "", | ||
| "policies:", | ||
| " - path: \"gate/policies/mcp_tool_allowlist.rego\"", | ||
| " - path: \"policies/mcp_tool_allowlist.rego\"", |
There was a problem hiding this comment.
Recording dir path not updated for config-relative resolution
Medium Severity
The policy path was changed from gate/policies/mcp_tool_allowlist.rego to policies/mcp_tool_allowlist.rego to account for gate-connector resolving paths relative to the config file (gate/connector.yaml). However, the recording.dir value ".data/gate-mcp-recordings" was not similarly adjusted. If gate-connector resolves all relative paths against the config location, this recording dir now resolves to gate/.data/gate-mcp-recordings instead of the project-root .data/gate-mcp-recordings. It likely needs to be "../.data/gate-mcp-recordings" to preserve the original behavior.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit cf511fa. Configure here.


Summary
policies/mcp_tool_allowlist.regoreferences relative togate/connector.yamlTesting
Pairs with evalops/gate path-resolution fixes so generated Gate configs work cleanly from a Gate checkout.