Veracode Profile Sandboxes Helper
ActionsTags
(2)Verified
An Action to handle Sandboxes mainly as a set of clean-up activities such as:
- Deleting a sandbox
- Delete Multiple Sandboxes
- Promoting Sandbox scan to Policy Scan
- with or without deleting the sandbox
❗ You will need to provide API credentials as environment variables. (See examples below)
Required - The name of the activity to perform
Available options value:
| Value | Details |
|---|---|
remove-sandbox |
Remove/Delete a sandbox |
promote-latest-scan |
Promote the latest Sandbox scan to a Policy |
clean |
Delete multiple dated sandboxes based on recent activity |
Required - The Veracode Application Profile name
Required - The sandbox name
Optional - Only works with activity: "promote-latest-scan" activity and give you the option to specify if you want the Sandbox to be deleted after the last scan is promoted to a Policy Scan
| Value | Details |
|---|---|
"false" |
Default - Do not delete the Sandbox |
"true" |
Delete the Sandbox after promoting the latest scan |
Optional - The number of dated sandboxes to delete. The query of sandboxes will target Sandboxes which their modified date is most dated.
| Value | Details |
|---|---|
1 |
Default - Delete a single Sandbox |
| Any number from 1-25 | Number of sandboxes to delete |
Optional - The attribute will instruct the clean step to only look for sandboxes which their modified date is older than the amount of days given as the a value.
:exclamation: Only works in conjunction with the clean activity
| Value | Details |
|---|---|
0 |
Default - Any sandbox |
| Any other number - X | Can only delete sandboxes which last modified at least X days ago |
For deleting a sandbox you can simply add the following step to your workflow job.
on:
delete: # a trigger for when a Branch is deleted
workflow_dispatch:
jobs:
veracode-sandbox-task:
runs-on: ubuntu-latest
name: Clean branch Sandbox
steps:
... # your other job steps
- name: Delete Sandbox
env:
VERACODE_API_ID: '${{ secrets.VERACODE_API_ID }}'
VERACODE_API_SECRET: '${{ secrets.VERACODE_API_SECRET }}'
uses: veracode/veracode-sandboxes-helper@v1.0.0
with:
activity: "remove-sandbox"
app-name: "<YOUR VERACODE APPLICATION NAME>"
# "${{ github.ref }}" - current branch on push triggers
# or "${{ github.event.pull_request.head.ref }}" - post pull request
sandbox-name: "<SANDBOX_NAME>"
Delete up to two most dated Sandboxes modified at least 14 days ago.
on:
workflow_dispatch:
schedule:
- cron: 30 14 * * *
jobs:
veracode-sandbox-maintenance-task:
runs-on: ubuntu-latest
name: Pull Request Review Submitted
steps:
... # your other job steps
- name: Delete old unused Sandboxes
env:
VERACODE_API_ID: '${{ secrets.VERACODE_API_ID }}'
VERACODE_API_SECRET: '${{ secrets.VERACODE_API_SECRET }}'
uses: veracode/veracode-sandboxes-helper@v1.0.0
with:
activity: "clean"
app-name: "<YOUR VERACODE APPLICATION NAME>"
clean-amount: "2"
clean-modified-before: "14"
For promoting a scan from Sandbox to a Policy you can use the following
on:
pull_request_review: # a trigger when a Pull Request Review submitted
types: [submitted]
workflow_dispatch:
jobs:
veracode-sandbox-task:
runs-on: ubuntu-latest
name: Pull Request Review Submitted
steps:
... # your other job steps
- name: Promote Scan on Approval
# run only if the pull request got approved
if: ${{ github.event.review.state == 'approved' }}
env:
VERACODE_API_ID: '${{ secrets.VERACODE_API_ID }}'
VERACODE_API_SECRET: '${{ secrets.VERACODE_API_SECRET }}'
uses: veracode/veracode-sandboxes-helper@v1.0.0
with:
activity: "promote-latest-scan"
app-name: "<YOUR VERACODE APPLICATION NAME>"
sandbox-name: "<SANDBOX_NAME>" # "${{ github.event.pull_request.head.ref }}"
delete-on-promote: true # Optional: also Deleting the Sandbox
Veracode Profile Sandboxes Helper is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.