Skip to content

feat(supabase): add database output filtering - #3283

Draft
esestamparia wants to merge 1 commit into
rtk-ai:developfrom
esestamparia:feat/supabase-db-filter
Draft

feat(supabase): add database output filtering#3283
esestamparia wants to merge 1 commit into
rtk-ai:developfrom
esestamparia:feat/supabase-db-filter

Conversation

@esestamparia

Copy link
Copy Markdown

Summary

  • add safe output filtering for selected supabase db and supabase migration list commands
  • register direct, npx, pnpm, and pnpx discovery and rewrite paths
  • preserve raw output for interactive, remote reset, terminal SQL diff, errors, and unknown formats
  • redact sensitive command arguments from RTK history and provide full-output guidance when truncating

Supported filters

  • supabase db lint
  • supabase db push --yes
  • supabase db push --dry-run
  • supabase db diff with -f, --file, -o, or --output
  • supabase db reset --local
  • supabase migration list

Safety

Interactive db push, terminal SQL output from db diff, remote or linked resets, failures, and unknown formats remain passthrough. Sensitive tokens, passwords, and database URLs are sanitized in history.

Validation

  • cargo fmt --all --check
  • cargo clippy --all-targets
  • cargo test (2514 passed, 8 ignored; integration guards 11 passed)
  • targeted filter and discovery tests
  • manual passthrough checks
  • git diff --check
  • representative output reduction: 66.9%

Relates to #1995

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants