Skip to content

feat(cli): migrate network bans#5382

Merged
Coly010 merged 4 commits into
supabase:developfrom
7ttp:feat/network-bans-port
May 29, 2026
Merged

feat(cli): migrate network bans#5382
Coly010 merged 4 commits into
supabase:developfrom
7ttp:feat/network-bans-port

Conversation

@7ttp
Copy link
Copy Markdown
Contributor

@7ttp 7ttp commented May 28, 2026

TL;DR

Ports supabase network-bans get and supabase network-bans remove from the Go proxy to native TypeScript

What's Introduced

Replaces the LegacyGoProxy path for both network-bans leaf commands with native handlers
wired through the existing legacy management-api runtime and instrumentation path

Coverage

Added a small integration suite covering this as well

@7ttp 7ttp requested a review from a team as a code owner May 28, 2026 17:48
@7ttp 7ttp self-assigned this May 28, 2026
- Correct get/SIDE_EFFECTS.md API method (POST .../retrieve, not GET)
- Document requester_ip in remove/SIDE_EFFECTS.md request body
- Add Files Written + Telemetry sections to both SIDE_EFFECTS.md files
- Hoist encodeBannedIpsToml to network-bans.encoders.ts with unit tests
- Add output.task spinner to get handler text mode (sibling parity)
- Reorder get handler branches and document --output pretty/json fallthrough
- Clarify remove handler precedence rule with explanatory comment
- Fill test coverage: yaml/json/pretty for get, network failures for both,
  --output-format stream-json for remove, telemetry/cache assertions on
  success and failure for both commands
Copy link
Copy Markdown
Contributor

@Coly010 Coly010 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! This was great work!

There were some minor things that appeared in my feedback, so I addressed them in the commit I added. Thanks again!

@Coly010 Coly010 merged commit 0684ae6 into supabase:develop May 29, 2026
8 checks passed
@7ttp 7ttp deleted the feat/network-bans-port branch May 29, 2026 11:25
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