fix(webapp): invalidate the webhook endpoint cache after a dashboard secret change

Rotating or generating a webhook signing secret from the dashboard now invalidates the engine's cached endpoint immediately, so deliveries are verified against the new secret right away instead of being rejected for up to the cache TTL. The HTTP API route already did this; the dashboard generate and set/rotate actions now match.

Author: ericallam

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.webhooks.endpoints.$endpointParam/route.tsx

@@ -46,6 +46,7 @@ import {
 } from "~/presenters/v3/WebhookDetailPresenter.server";
 import { clickhouseFactory } from "~/services/clickhouse/clickhouseFactoryInstance.server";
 import { getSecretStore } from "~/services/secrets/secretStore.server";
+import { webhookEngine } from "~/v3/webhookEngine.server";
 import { requireUser } from "~/services/session.server";
 import { docsPath, EnvironmentParamSchema, v3WebhookTaskPath } from "~/utils/pathBuilder";
 import { parseFiniteInt } from "~/utils/searchParams";
@@ -180,6 +181,7 @@ export const action = async ({ request, params }: ActionFunctionArgs) => {
       where: { id: endpoint.id },
       data: { signingSecretKey: secretKey },
     });
+    webhookEngine.invalidateEndpoint(endpoint.opaqueId);
     return { success: true as const, generatedSecret: secret };
   }
 
@@ -193,6 +195,7 @@ export const action = async ({ request, params }: ActionFunctionArgs) => {
     where: { id: endpoint.id },
     data: { signingSecretKey: secretKey },
   });
+  webhookEngine.invalidateEndpoint(endpoint.opaqueId);
 
   return { success: true as const };
 };