From e98410dfd7195d939594bdf346aa4bbcdf31028f Mon Sep 17 00:00:00 2001
From: Ian Littman <iansltx@gmail.com>
Date: Tue, 20 Aug 2024 16:00:54 -0500
Subject: [PATCH] Add VSCode launch configuration for debugging vuln_processing
 command (#21305)

This is an easy way to debug the various vulnerabilities ETLs that we'd
normally execute as an in-app cron. I used this over the weekend to test
#21242.

# Checklist for submitter

- [x] Manual QA for all new/changed functionality
---
 .vscode/launch.json | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/.vscode/launch.json b/.vscode/launch.json
index 3e3ac95d6a..885f407fb8 100644
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -61,6 +61,21 @@
                 "--dev_license"
             ]
         },
+        {
+            "name": "Fleet vuln_processing (licensed)",
+            "type": "go",
+            "request": "launch",
+            "mode": "auto",
+            "buildFlags": "-tags='full,fts5'",
+            "cwd": "${workspaceFolder}",
+            "program": "${workspaceFolder}/cmd/fleet",
+            "args": [
+                "vuln_processing",
+                "--dev",
+                "--logging_debug",
+                "--dev_license",
+            ]
+        },
         {
             "name": "Attach to a running Fleet server",
             "type": "go",