Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Deleting a resource leaves the policies granted on it

未关闭
  • 哪里不对？
#1,993 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
62/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
authorization, backend

调研方向

Start with Delete and Purge in core/resource/service.go, which remove the resource's relations and row but never touch the policy service. Reproduce the steps with CreatePolicy, DeleteProjectResource, then ListPolicies and GetPolicy, and check the policy rows and role binding relations that remain. Done means that deleting a resource, directly or through the project delete cascade, also removes its policies, and ListPolicies no longer returns them.

由索引模型根据 Issue 内容生成。

描述

Deleting a resource removes its SpiceDB relations and soft-deletes its row. Policies granted on the resource are not deleted. Their rows and their two role binding relations stay, and ListPolicies still returns them. They no longer grant anything, because the link from the resource to the role binding is gone.

The project delete cascade purges project resources the same way, so policies on them stay too.

Steps

  1. Create a resource and grant a user a role on it with CreatePolicy.
  2. Delete the resource with DeleteProjectResource.
  3. ListPolicies for the user still returns the policy, and GetPolicy still finds it.

Code
Delete and Purge in core/resource/service.go delete the resource's relations and row, but never call the policy service.

Expected
Deleting a resource also deletes the policies on it.

主要语言
Go
星标
343
派生
48
平均合并
2 天 9 小时
30 天内合并 PR
48

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

raystack/frontier 的其他 Issue

查看 raystack/frontier 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。