Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run configuration: improve the way we handle bundle dir #87

Open
vgramer opened this issue Jan 14, 2021 · 1 comment
Open

run configuration: improve the way we handle bundle dir #87

vgramer opened this issue Jan 14, 2021 · 1 comment

Comments

@vgramer
Copy link
Member

vgramer commented Jan 14, 2021

What would you like to be added

  1. rename bundle to source directory in the UI� (using OPA doesn't mean you ever used bundles, so that concept may be unfamiliar.)
  2. set the default value of bundleDir to the workspace directory. In the case where the project contains only opa files, it allows to eval / test policies in one click.

note: if bundleDir 's value is defined in the run configuration template, we must not overwrite it

@frangauthiercgi
Copy link

+1 on this

Here is my issue:
Our project is only used for OPA policies writing. To test we use the command opa test project_directory/ -v but we are unable to reproduce the same outcome using the plugin.
Bundle parameter seems mandatory and our tests are failing when specifying a Bundle path.
An option to set the bundle parameter as optional and using the project root as default would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants