Absolute paths do not work with rego.Load on Windows

[lcarva]

Short description

When using rego.Load with an absolute path on Windows, the following error is returned when Rego.PrepareForEval is called:

1 error occurred during loading: CreateFile \Users\RUNNER~1\AppData\Local\Temp\TestRegoPolicyLoadAbsolutePath3698015745\001\policy.rego: The system cannot find the path specified.

The issue does not occur if a relative path is used. The issue does not work on Linux or OSX.

Steps To Reproduce

policy := `
	package signature

	allow {
		input.predicateType == "https://slsa.dev/provenance/v0.2"
	}
`
// This alternative line works:
// policyFile := "policy.rego"
policyFile := filepath.Join(t.TempDir(), "policy.rego")
if err := os.WriteFile(policyFile, []byte(policy), 0644); err != nil {
	t.Fatal(err)
}
r := rego.New(rego.Query("data.signature.allow"), rego.Load([]string{policyFile}, nil))

ctx := context.Background()

// This fails on Windows Server 2022.
_, err := r.PrepareForEval(ctx)
if err != nil {
	t.Fatal(err)
}

Expected behavior

PrepareForEval should not return an error.

Additional context

I created a small git repo to reproduce this issue. The test TestRegoPolicyLoadAbsolutePath fails, while the test TestRegoPolicyLoadRelativePath passes. The GitHub actions were useful in running the tests across different Operating Systems. I'm not sure how long the results will last, but here's a link to them.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[anderseknert]

Hey @lcarva! Sorry for not acknowledging this before, but that definitely seems like a bug. If anyone with a Windows machine would consider taking a look at this, that would be much appreciated!

[lcarva]

@anderseknert, no worries! FWIW, it's possible to reproduce the issue with just GitHub actions as mentioned in the description. It's definitely not as easy to debug as a local system, but a potential way forward.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[lcarva]

Still failing on opa v0.40.0 with the same error.

[anderseknert]

Yes, no changes here, @lcarva. The stalebot warning does not mean it's being closed/removed, just that there's not been any activity for some time.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days.

[simar7]

Still seems to be the case on v0.54.0.

[stale]

This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.