Something went wrong. Try again.
[READ-ONLY] Mirror of https://github.com/openstatusHQ/openstatus. 🫖 Status page with uptime monitoring & API monitoring as code 🫖 openstatus.dev
bun drizzle-orm monitoring monitoring-as-code nextjs observability on-call open-source shadcn-ui status-page statuspage synthetic-monitoring tinybird turso uptime uptime-checker uptime-monitor
Something went wrong. Try again.
1.0 kB · 31 lines
TypeScript
at incident-api
1234567891011121314151617181920212223242526272829303132import type { ServiceContext } from "../context";import { type AddStatusReportUpdateResult, addStatusReportUpdate,} from "./add-update";import { ResolveStatusReportInput } from "./schemas";
/** * Convenience over addStatusReportUpdate with status="resolved". Exists so * Slack's `resolveStatusReport` action has a named call site with matching * intent; audit action is still `status_report_update.create` (same db path). * * No scope check here: the delegate (`addStatusReportUpdate`) enforces * `requireScope(ctx, 'write')` itself, and a wrapper double-check is * pure noise. */export async function resolveStatusReport(args: { ctx: ServiceContext; input: ResolveStatusReportInput;}): Promise<AddStatusReportUpdateResult> { const input = ResolveStatusReportInput.parse(args.input); return addStatusReportUpdate({ ctx: args.ctx, input: { statusReportId: input.statusReportId, status: "resolved", message: input.message, date: input.date, }, });}