Skip to content

chore: pass schemas to opa test #386

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

Merged
merged 3 commits into from
May 27, 2025
Merged

Conversation

nikpivkin
Copy link
Contributor

No description provided.

Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
@nikpivkin
Copy link
Contributor Author

This PR will be ready for review when we remove Trivy from the dependencies.

@simar7
Copy link
Member

simar7 commented Apr 10, 2025

interesting, what does passing the schema to the tests do differently? Is it able to type check?

@nikpivkin
Copy link
Contributor Author

Yes, passing the schema to the tests performs type checking. This works the same way as it does now inside Trivy by passing the schema in compile checks. Right now the schema is checked by Trivy itself in some Go tests. But in the future, when we remove Trivy from dependencies, we will need to pass the schema to OPA for type checking.

@nikpivkin
Copy link
Contributor Author

It may be better to pass the schema to opa check.

Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
@nikpivkin nikpivkin marked this pull request as ready for review May 26, 2025 11:02
@nikpivkin nikpivkin requested a review from simar7 as a code owner May 26, 2025 11:02
@simar7 simar7 added this pull request to the merge queue May 27, 2025
Merged via the queue into aquasecurity:main with commit 6042485 May 27, 2025
5 checks passed
@nikpivkin nikpivkin deleted the trivy-schemas branch May 27, 2025 03:40
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

Successfully merging this pull request may close these issues.

2 participants