Rules and input in sub-directory doesn't work

[mhausenblas]

I'm working on mhausenblas/eunomia/ and when I issue the query on the command line, in the respective sub-dir I get the expected result:

opa eval --input input.json --data violations.rego --package violations.eunomia.testing 'rbac_cluster_role'

However, with the VSCode plug-in I get:

// Evaluated package in 763.04µs.
{
  "rbac_cluster_role": []
}

I tried to set opa.roots in settings.json to ${fileDirname} but that didn't help either.

[patrick-east]

I think things are working as intended.

The VSCode integration current looks at the workspace root for a file called input.json which it will use as the input for evaluations. If you open vscode only on the ./test directory it works as expected, for example:

What would be helpful is if we could adjust the plugin tasks to allow providing a different/custom input document. That seems like the right way to make this work more as expected (along with #26 so that its easier to see what actually was being run)

In the meantime for your project you can always just make custom VSCode tasks like:

.vscode/tasks.json:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "eval rbac_cluster_role",
            "type": "shell",
            "command": "opa eval --input ./test/input.json --data ./test/violations.rego --package violations.eunomia.testing rbac_cluster_role"
        }
    ]
}

Which you can invoke via the command pallete

And get your results in vscode:

[patrick-east]

I filed #28 to track adding some way to provide custom input paths.

[mhausenblas]

Thanks a million for the very speedy follow up and resolution, really appreciate it @patrick-east ... I shall subscribe to #28 ;)