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

opa eval -b does not honor the --ignore flag #6358

Open
anderseknert opened this issue Oct 30, 2023 · 1 comment
Open

opa eval -b does not honor the --ignore flag #6358

anderseknert opened this issue Oct 30, 2023 · 1 comment

Comments

@anderseknert
Copy link
Member

anderseknert commented Oct 30, 2023

❯ tree
.
├── p.rego
└── t.rego

1 directory, 2 files

Using a intentionally broken t.rego file, the following works for opa eval:

❯ opa eval -f pretty -d . --ignore t.rego data.p.allow
true

But using the -b/--bundle options does not:

❯ opa eval -f pretty -b . --ignore t.rego data.p.allow
1 error occurred: loading error: bundle .: 1 error occurred: t.rego:3: rego_parse_error: var cannot be used for rule name

Similar issues have been reported before for opa build (fixed) and opa test, but I could not find an issue reported for opa eval.

This issue was reported first in the OPA VS Code plug-in by @Ronnie-personal, where we sometimes have seen errors reported, and performance issues, caused by .git and other irrelevant directories and files getting included in the workspace bundle.

Copy link

stale bot commented Nov 29, 2023

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.

@stale stale bot added the inactive label Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant