Is your feature request related to a problem? Please describe.
enabling MRN is normally non-destructive
However there is a gap in TF where you cannot use TF to add region to an existing Namespace.
Note that Manual failovers (e.g., for testing) should still be triggered in the UI / API / CLI and then synced back to Terraform.
Describe the solution you'd like
Being able to add region to a namespace safely, meaning we should avoid accidental "terraform apply" that actually cause an HA migration (e.g. trigger replication/region changes)
e.g. enable the new region via the UI/CLI (staging first), wait for replication to become healthy, then terraform refresh/plan so Terraform picks up the change.
deal state
- would be being able to add the replica region to support MRN without having to ignore/un-ignore yea.
Additional context
https://temporaltechnologies.slack.com/archives/C03CP9DDKD4/p1771011577106699?thread_ts=1770916541.632949&cid=C03CP9DDKD4
Is your feature request related to a problem? Please describe.
enabling MRN is normally non-destructive
However there is a gap in TF where you cannot use TF to add region to an existing Namespace.
Note that Manual failovers (e.g., for testing) should still be triggered in the UI / API / CLI and then synced back to Terraform.
Describe the solution you'd like
Being able to add region to a namespace safely, meaning we should avoid accidental "terraform apply" that actually cause an HA migration (e.g. trigger replication/region changes)
e.g. enable the new region via the UI/CLI (staging first), wait for replication to become healthy, then terraform refresh/plan so Terraform picks up the change.
deal state
Additional context
https://temporaltechnologies.slack.com/archives/C03CP9DDKD4/p1771011577106699?thread_ts=1770916541.632949&cid=C03CP9DDKD4