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

Delete Temporal Cloud namespaces per deletion policy

已关闭
#9 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 2 天内回复

@niyomukiza-mechack 已经在做这个了。

开始于 2026年10月19日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, kubernetes

调研方向

Start by settling the deletion policy the issue leaves open: check how the Namespace CR's deletion policy field is defined and what the Temporal Cloud client exposes for deleting a namespace. The change then goes in the controller's finalizer path, which must keep the CR until Temporal Cloud reports deletion complete. Done means unit tests with the fake client cover Retain, Delete, and the case where the operator didn't create the namespace.

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

描述

Goal

Deleting a Namespace CR does what its deletion policy states, and must not delete a namespace the operator didn't create.

Tasks

  • Decide the deletion policy (what happens in Temporal Cloud when a user deletes a Namespace CR)
  • Delete the namespace in Temporal Cloud when the policy says so
  • Keep the CR until Temporal Cloud has finished deleting

Definition of done

  • If the deletion policy is Retain (the default), deleting the CR leaves the namespace in Temporal Cloud.
  • If the deletion policy is Delete, deleting the CR removes the namespace from Temporal Cloud.
  • A namespace the operator didn't create is never deleted.
  • Unit tests cover both policies and the failure cases using the fake client.
主要语言
Go
星标
1
派生
0
平均合并
2 天 16 小时
30 天内合并 PR
16

环境准备

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

从这里开始

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

temporalio/cloud-operator 的其他 Issue

查看 temporalio/cloud-operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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