fix: don't force-resolve config after agent startup

Signed-off-by: Sam Gammon <[email protected]>
buildless · Dec 5, 2023 · 3f69e07 · 3f69e07
1 parent f2f6241
commit 3f69e07
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 12 deletions.
diff --git a/dist/cleanup/index.js b/dist/cleanup/index.js
diff --git a/dist/cleanup/index.js.map b/dist/cleanup/index.js.map
diff --git a/dist/index.js b/dist/index.js
diff --git a/dist/index.js.map b/dist/index.js.map
diff --git a/src/main.ts b/src/main.ts
@@ -292,14 +292,7 @@ async function setupAgentIfNeeded(
         }
       }
       if (!installFailed && !startFailed) {
-        const cfg = await agentConfig()
-        if (!cfg) {
-          console.warn(
-            `Agent started at PID ${pid}, but config failed to resolve. Caching may not work.`
-          )
-        } else {
-          core.info(`Agent installed and started at PID: ${pid}.`)
-        }
+        core.info(`Agent installed and started at PID: ${pid}.`)
         agentEnabled = true
         agentManaged = true
       }