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
Kubescape fix not working #1392
Comments
@corvusmod I am trying to reproduce this with no success. Can you try to run the
|
I think I identified the problem, but it doesn't seem related to fix argument. These are my test:
kubescape scan . --format json --output output.json ✅ Initialized scanner And if I run fix against this json kubescape fix /Users/redacted/sources/kk/output.json ℹ️ Reading report file... BUT... I deleted .git folder and then. git init, git add all files and git commit... kubescape scan . --format json --output output.json ✅ Initialized scanner And fix... WORK!!!! kubescape fix /Users/redacted/sources/kk/output.json So there is something related to git configuration when it can't connect with an internal gitlab server. I hope that you can identify the problem. Also, there is any way to disable git scan when you only want to test local files even then this folder has git configuration? Thanks |
Interesting!
I will first need to understand the root cause because the fact that you are scanning a git repo should not affect the results. |
Description
fix command is not working
Environment
OS:
MacOS
Version:
2.9.1
Steps To Reproduce
Following the steps when running kubescape fix -h
Expected behavior
Yamls modified with the fixed detected
Actual Behavior
Error getting json file
`1)
✅ Scan results saved. filename: output.json
Overall compliance-score (100- Excellent, 0- All failed): 76
➜ ls -la output.json
-rw-r--r--@ 1 luis.cuervo staff 225865 Sep 18 14:37 output.json
➜ kubescape fix output.json
ℹ️ Reading report file...
Error: stat : no such file or directory
Usage:
kubescape fix [flags]
`
Additional context
Tried in several projects and always the same result.
The text was updated successfully, but these errors were encountered: