test(e2e): org delete hides the kyc row

[rohilsurana]

Summary

Deleting an org should also delete its KYC record. No end to end test checked this. This PR adds one.

Changes

• New e2e test TestOrganizationDeleteHidesItsKyc.
• The API regression suite now opens a database connection, so a test can look at rows the API does not show.

Technical Details

The test sets KYC on an org and deletes the org. It then checks four things.

• The deleted org is not in the KYC list.
• Reading the KYC of the deleted org gives an error, or an empty record.
• The organizations_kyc row is still in the database, with deleted_at set and no live row left.
• Setting KYC on the deleted org is refused, and a new org with the same name starts with no KYC.

The database check is the one that matters. The org is soft deleted too, so the API alone cannot tell whether the cascade deleted the KYC row. I made the org delete skip the KYC step for a moment. Only the database check failed, which shows it works. I then removed that change.

This test passes on main already. It documents current behaviour and guards it.

Test Plan

• go test ./test/e2e/regression -run TestEndToEndAPIRegressionTestSuite -testify.m TestOrganizationDeleteHidesItsKyc passes
• Same test fails when the org delete skips the KYC delete (change reverted)
• go vet ./test/e2e/...
• golangci-lint run ./test/e2e/... reports 0 issues
• gofmt -l test/e2e reports nothing

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
frontier	Ready	Preview	Oct 16, 2026 10:09am UTC

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: raystack/frontier/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: c023c987-9733-4c67-8a47-a510342e6389

📥 Commits

Reviewing files that changed from the base of the PR and between 22db2fd and ea0b626.

📒 Files selected for processing: 1

• test/e2e/regression/api_test.go

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

• Tests
  • Added regression coverage verifying that deleting an organization hides its KYC information and prevents access to it.
  • Verified KYC updates are rejected for deleted organizations, and that recreating an organization under the same name does not restore its prior KYC information. These checks confirm the expected behavior across organization deletion and recreation.

The regression suite now owns a database client. A new test checks KYC behavior when an organization is deleted and recreated with the same name.

Changes: Organization KYC deletion

Layer / File(s)	Summary
Database-backed deletion regression test/e2e/regression/api_test.go	The suite opens and closes a database client. The new test checks that organization deletion hides KYC, leaves a soft-deleted database row, rejects KYC updates to the deleted organization, and does not restore KYC when the organization is recreated.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: amangit07, whoabhisheksah

Merge Risk: ⚪ Minimal · up to ea0b6

No actionable issue is established that should delay merging this regression test after normal checks.

Pre-merge checks: 2

Check name	Status	Explanation
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coveralls]

Coverage Report for CI Build 38885275238

Coverage remained the same at 55.248%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	41723
Covered Lines:	23051
Line Coverage:	55.25%
Coverage Strength:	19.16 hits per line

---

💛 - Coveralls