How to Configure Make CockroachDB Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

You can set up a make cockroachdb approval flow by pairing a review webhook with database roles. This flow holds SQL changes until a reviewer clicks approve in a chat app. Many teams build this setup to stop bad queries before they hit production data. Still, most automated scenarios still log in with one shared database role. When that role has broad permissions, any approved step can alter or drop whole tables. How a native make cockroachdb approval workflow operates Make runs automated sce

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You can set up a make cockroachdb approval flow by pairing a review webhook with database roles. This flow holds SQL changes until a reviewer clicks approve in a chat app. Many teams build this setup to stop bad queries before they hit production data. Still, most automated scenarios still log in with one shared database role. When that role has broad permissions, any approved step can alter or drop whole tables.

How a native make cockroachdb approval workflow operates

Make runs automated scenarios that link cloud apps and databases together in a visual builder. CockroachDB is a distributed SQL database that uses roles and grants to control user actions. To link them, a team first creates a dedicated database user with specific table grants. The team then stores those database login details inside the scenario builder.

When a trigger fires, the scenario pauses before it runs the database step. It sends a message to a team channel or email inbox asking for a review. A team lead reads the details and clicks a link to approve the run. That click hits a webhook that tells the paused scenario to move forward. The scenario then logs in to CockroachDB and runs the SQL statement.

How database roles and scenario webhooks work together

CockroachDB checks permissions when a client logs in and starts a query. You can grant read permissions on one table and write permissions on another table. You can also group these grants into a role and assign it to the automation user. This ensures the scenario can only touch the tables it needs for its job.

In the scenario builder, each step passes data to the next step in the flow. A webhook step waits for an external signal before it passes data to the database step. You can set a time limit on this wait so stale requests fail on their own. If the reviewer clicks reject, the scenario stops and logs the rejected request. If the reviewer approves, the database step opens a session and sends the SQL query.

What native setups solve and what they leave open

This native setup solves two basic problems for data teams. First, CockroachDB roles stop unauthorized users from logging in to the database cluster. Second, the scenario webhook stops automated tasks from running without a human check. Together, they give teams a basic way to gate automated workflows.

Approval Chains & Escalation + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Yet this setup leaves a major gap during the actual database session. Database roles decide who can log in, not what each individual statement does in flight. Once the scenario logs in with write rights, it can run any allowed query. A bug in the scenario mapping could overwrite thousands of rows instead of one row. The reviewer only sees the summary sent in the chat message, not the raw SQL query.

Also, the scenario stores long-lived database keys to run its tasks. If someone edits the scenario and skips the webhook step, the database will still run the query. CockroachDB only sees a valid login from the shared automation user. It cannot tell which person clicked approve or if a webhook check even took place. Also, standard query results return raw values like emails, phone numbers, and card numbers. Those sensitive fields flow straight back into the scenario run history in plain text.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.

First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Can CockroachDB pause a single SQL query for human review on its own?

No, CockroachDB checks role grants right away and runs valid queries without pausing. You need an external workflow or review tool to hold a query before it runs.

Why is a shared database user risky in automated scenarios?

A shared user ties every action in the database log to one single account name. When a bad query runs, your audit log will not show which team member approved it.

How does data masking help when scenarios read from CockroachDB?

Data masking rewrites matched fields like emails and card numbers in query results. This keeps raw user data out of your third-party workflow logs and chat tools.

The query runs. The emails stay hidden.