Add Kubesec workflow for security scanning - #287
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: Run kubesec scanner | ||
| uses: controlplaneio/kubesec-action@43d0ddff5ffee89a6bb9f29b64cd865411137b14 | ||
| with: | ||
| input: file.yaml # specify configuration file to scan here | ||
| format: template |
There was a problem hiding this comment.
The workflow hardcodes input: file.yaml, but this repository does not contain that file (find . -name 'file.yaml' returns nothing), so the kubesec action will attempt to scan a missing path and the step will fail before producing SARIF on every push/PR/scheduled run. The scanner never reaches real manifests, so the new security job provides no coverage.
Useful? React with 👍 / 👎.
No description provided.