Support disabling and deletion of namespaces

[rfwagner]

Temporal should support different stages of namespace deletion.

It is inevitable over time that namespaces are created with typos, are abandoned etc. These namespaces clutter up the UI and can cause confusion over whether they are active.

Possible stages of namespace deletion:

1. Disable a namespace: make it no longer possible to submit new workflows to a namespace
2. Disable and hide namespace: same as above, but also suppress the namespace from the "namespace list" API's
3. Soft delete. Delete a namespace but do it in such a way that undelete is possible
4. Hard delete. Remove the namespace from the db with no possibility of undelete

4 (and maybe 3?) would require a crawl of the db to ensure there are no references to the namespace, in the form of active or unarchived workflows.

[davidalpert]

this ability would be super duper helpful for people learning about temporalio as it is easy to create namespace before thinking through or even understanding consequences of a naming strategy.

the ability to rename or delete namespaces is pretty important in that sense to make experimentation cheaper.

at this point it seems that my only option is to drop the temporal database and recreate it using the schema migration tools

[tristan-instacart]

Just having requirements 1 and 2 would be extremely beneficial for operations in larger organizations, even if we have to wait longer for requirements 3 and 4.

[tsurdilo]

Any info on this issue? Associated forum link - https://community.temporal.io/t/how-to-delete-a-namespace/677

[calum-stripe]

Any update on this?

[antstorm]

+1

[franklinkim]

+1

[dwillett]

+1

[alexshtin]

Delete namespace functionality was released in 1.17.0.

[kenske]

~~Was this actually released? The release page for 1.17.0 says not to use it, and even on 1.18.0 there is no delete command for tcl namespace.~~

Namespaces can be deleted using the temporal command:

temporal operator namespace delete my-namespace