[AmanGIT07]

Summary

The project delete now publishes the app.project.deleted event. The event name already existed and is offered as a webhook event, but nothing published it; project created, updated, and member events were already published. It goes out once the project row is deleted, for the DeleteProject RPC and for each project an organization delete removes, the same way the organization delete publishes app.organization.deleted. Stacked on #2013.

Changes

• core/deleter/service.go: after DeleteModel, deleteProject publishes app.project.deleted with the project as the target and the project's organization. A project that was already gone returns without an event. A failure to publish is logged and does not fail the delete.

Test Plan

• core/deleter/service_test.go TestDeleteProject: a delete publishes one app.project.deleted event with the project's organization and the project as the target; a project that was already gone publishes nothing.
• e2e TestProjectDeleteKeepsTheRowAndRemovesAccess: one app.project.deleted event for the project after the delete.
• e2e TestOrganizationDeleteAlsoDeletesDisabledProjectsAndGroups: one app.project.deleted event for each project of the deleted organization, the disabled one included.
• Without the publish, the unit case and both e2e checks fail.
• go test ./core/... ./internal/api/... ./pkg/server/... passes.
• e2e TestEndToEndAPIRegressionTestSuite, TestEndToEndServiceUsersRegressionTestSuite and TestEndToEndPATRegressionTestSuite pass.
• golangci-lint run ./core/deleter/... ./test/e2e/regression/... reports no issues.

[vercel]

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

Project	Deployment	Actions	Updated
frontier	Ready	Preview	Oct 23, 2026 3:31am UTC

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 50 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Source mode: Auto
• Repository: raystack/frontier
• Branch: main
• File: .coderabbit.yaml
• Commit: 7338205
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7ba51d00-11d1-44ff-8cb9-d3ae211a93d1

📥 Commits

Reviewing files that changed from the base of the PR and between 7338205 and ebe0dd5.

📒 Files selected for processing: 3

• core/deleter/service.go
• core/deleter/service_test.go
• test/e2e/regression/api_test.go

• 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 39895435488

Coverage remained the same at 55.72%

Details

• Coverage remained the same as the base build.
• Patch coverage: 2 uncovered changes across 1 file (5 of 7 lines covered, 71.43%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
core/deleter/service.go	7	5	71.43%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	41922
Covered Lines:	23359
Line Coverage:	55.72%
Coverage Strength:	19.35 hits per line

---

💛 - Coveralls

[AmanGIT07]

Sandbox run: a local Frontier server with Postgres and SpiceDB in Docker, called over the Connect protocol. The binary was built from #2014 with #2011 applied, so it has main plus #2008, #2011, #2013 and #2014.

Deletion config used (for the projects with resources):

app:
  deletion:
    enabled: true
    resources:
      resource/aoi: { project: block, organization: allow }
      resource/workflow: { project: block, organization: allow }
      resource/orderitem: { project: block_unless_deletable, organization: block_unless_deletable }
      resource/insight: { project: allow, organization: allow }

resource/report has no rule.

app.project.deleted events

Counted in the auditlogs table (log.audit_events: db).

Check	Expected	Observed
Delete an empty project	1	1
Delete a project after its blocking resources were deleted	1	1
Delete a disabled project holding an insight	1	1
Delete an org with two projects, one disabled: events per project	1, 1	1, 1

The project.deleted audit records for the same deletes were written as before:

Check	Expected	Observed
Delete an empty project: project.deleted audit records	1	1
Delete an org with two projects: audit records per project	1, 1	1, 1