From 2aa299e01f7f085151609df4360dad15393e23ab Mon Sep 17 00:00:00 2001
From: kmcca <75409788+kmcca@users.noreply.github.com>
Date: Fri, 15 Mar 2024 16:20:01 -0400
Subject: [PATCH] Update veracode.yml

---
 veracode.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/veracode.yml b/veracode.yml
index 0a6665d..f3143f3 100644
--- a/veracode.yml
+++ b/veracode.yml
@@ -22,7 +22,7 @@ veracode_static_scan:
   # As an App Profile - given the current name of your scanned repo
   # Use 'none' if you would not like any scans saved to the platform
   analysis_branch: ENTER_BRANCH_NAME_HERE
-  analysis_on_platform: false
+  analysis_on_platform: true
   #If break_build_invalid_policy is set to true, the build will break when the policy name is invalid.
   break_build_invalid_policy: true
   #If the break_build_on_error is set to true, the build will break if the scan failed to complete in time or with an error.
@@ -36,13 +36,13 @@ veracode_static_scan:
   # workflow for each repository.
   use_custom_workflow: WORKFLOW_NAME
   #If the create_code_scanning_alert is set to true, code scanning alert for static findings will be created under GitHub Security.
-  create_code_scanning_alert: false
+  create_code_scanning_alert: true
   #If the create_issue is set to true, GitHub Issues will be created for static findings.
-  create_issue: false
+  create_issue: true
   profile: ENTER_PROFILE_NAME
   #If the trigger is set to true, the scan will be triggered when a command matches by either creating an issue or adding a comment to an issue.
   issues:
-    trigger: false
+    trigger: true
     commands:
       - "ENTER_COMMAND_TO_EXECUTE_SCAN"