Changed cache to be every 5 items in stead of 0xA #541
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# A sample workflow which checks out your Infrastructure as Code Configuration files, | |
# such as Kubernetes, Helm & Terraform and scans them for any security issues. | |
# The results are then uploaded to GitHub Security Code Scanning | |
# | |
# For more examples, including how to limit scans to only high-severity issues | |
# and fail PR checks, see https://github.com/snyk/actions/ | |
name: Snyk Infrastructure as Code | |
on: | |
push: | |
branches: [ main ] | |
pull_request: | |
# The branches below must be a subset of the branches above | |
branches: [ main ] | |
schedule: | |
- cron: '43 9 * * 1' | |
jobs: | |
snyk: | |
runs-on: ubuntu-latest | |
steps: | |
- uses: actions/checkout@v2 | |
- name: Run Snyk to check configuration files for security issues | |
# Snyk can be used to break the build when it detects security issues. | |
# In this case we want to upload the issues to GitHub Code Scanning | |
continue-on-error: true | |
uses: snyk/actions/iac@master | |
env: | |
# In order to use the Snyk Action you will need to have a Snyk API token. | |
# More details in https://github.com/snyk/actions#getting-your-snyk-token | |
# or you can signup for free at https://snyk.io/login | |
SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }} | |
with: | |
# Add the path to the configuration file that you would like to test. | |
# For example `deployment.yaml` for a Kubernetes deployment manifest | |
# or `main.tf` for a Terraform configuration file | |
file: your-file-to-test.yaml | |
- name: Upload result to GitHub Code Scanning | |
uses: github/codeql-action/upload-sarif@v1 | |
with: | |
sarif_file: snyk.sarif |