Skip to content
Recued
Menu
← Back to recipes

Suspend a Neon compute endpoint

by recued-core v1

Approval-gated Neon compute suspend workflow for one endpoint. It reads the endpoint for context, then calls recued-core.neon.endpoint.suspend for exactly that endpoint. It does not delete endpoints, change branches, reveal passwords, retrieve connection URIs, create resources, or call arbitrary Neon APIs.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)
normalized_project_id trim
Trim whitespace from setting project id
normalized_endpoint_id trim
Trim whitespace from setting endpoint id
normalized_reason trim
Trim whitespace from setting reason
endpoint_before ?
suspend ?
operations default
Apply default
operation_rows slice
Take a subset of
operation_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

neon setting =
reason setting =
project id setting =
endpoint id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Neon connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

neon neonpostgresdatabasecomputecost-controlapprovalpack:neon

Details

9 steps 4 configurable settings recipe_id: suspend-neon-compute