From a7a1d36e712d0303d74c0566801b3222faad658f Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Thu, 21 Nov 2024 08:01:50 +0100 Subject: [PATCH 1/4] Update clusters.md These statements conflict each other. --- versioned_docs/version-8.6/components/concepts/clusters.md | 1 - 1 file changed, 1 deletion(-) diff --git a/versioned_docs/version-8.6/components/concepts/clusters.md b/versioned_docs/version-8.6/components/concepts/clusters.md index b54b14f348f..8b700998a51 100644 --- a/versioned_docs/version-8.6/components/concepts/clusters.md +++ b/versioned_docs/version-8.6/components/concepts/clusters.md @@ -77,7 +77,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. - Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. From cde911d066742adfc9faa9a0359e688a823c31f6 Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Thu, 21 Nov 2024 08:41:14 +0100 Subject: [PATCH 2/4] fix(docs): remove inaccurate statements --- docs/components/concepts/clusters.md | 2 -- versioned_docs/version-8.3/components/concepts/clusters.md | 2 -- versioned_docs/version-8.4/components/concepts/clusters.md | 2 -- versioned_docs/version-8.5/components/concepts/clusters.md | 2 -- 4 files changed, 8 deletions(-) diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 59408dc166f..16c7e6a77a2 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -76,8 +76,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. diff --git a/versioned_docs/version-8.3/components/concepts/clusters.md b/versioned_docs/version-8.3/components/concepts/clusters.md index f0348b30820..7bd3ce5deea 100644 --- a/versioned_docs/version-8.3/components/concepts/clusters.md +++ b/versioned_docs/version-8.3/components/concepts/clusters.md @@ -38,8 +38,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. diff --git a/versioned_docs/version-8.4/components/concepts/clusters.md b/versioned_docs/version-8.4/components/concepts/clusters.md index db4bad1a4af..94ba72f05f1 100644 --- a/versioned_docs/version-8.4/components/concepts/clusters.md +++ b/versioned_docs/version-8.4/components/concepts/clusters.md @@ -38,8 +38,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. diff --git a/versioned_docs/version-8.5/components/concepts/clusters.md b/versioned_docs/version-8.5/components/concepts/clusters.md index bef1699122d..c1febb23115 100644 --- a/versioned_docs/version-8.5/components/concepts/clusters.md +++ b/versioned_docs/version-8.5/components/concepts/clusters.md @@ -38,8 +38,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. From 665c36395619dce76de01a5e1c3604314d34dd84 Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Thu, 21 Nov 2024 08:43:46 +0100 Subject: [PATCH 3/4] fix(docs): remove inaccurate statements --- versioned_docs/version-8.2/components/concepts/clusters.md | 6 ++++-- versioned_docs/version-8.6/components/concepts/clusters.md | 1 - 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-8.2/components/concepts/clusters.md b/versioned_docs/version-8.2/components/concepts/clusters.md index 7d96ec32d5e..a9b0c153138 100644 --- a/versioned_docs/version-8.2/components/concepts/clusters.md +++ b/versioned_docs/version-8.2/components/concepts/clusters.md @@ -37,8 +37,10 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. -- No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. +- Cluster disk space is cleared when a trial cluster is paused. + - You will need to redeploy processes to the cluster once it is resumed from a paused state. + - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. + :::tip To prevent auto-pause, [Upgrade your Free Trial plan](https://camunda.com/pricing/) to a Starter or Enterprise plan. diff --git a/versioned_docs/version-8.6/components/concepts/clusters.md b/versioned_docs/version-8.6/components/concepts/clusters.md index 8b700998a51..2df77d72957 100644 --- a/versioned_docs/version-8.6/components/concepts/clusters.md +++ b/versioned_docs/version-8.6/components/concepts/clusters.md @@ -76,7 +76,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. -- Paused `dev` (or untagged) clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. - Cluster disk space is cleared when a trial cluster is paused. - You will need to redeploy processes to the cluster once it is resumed from a paused state. - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. From f799adfa9b0b86a7a9777f064123041b6f28ec14 Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Thu, 21 Nov 2024 09:06:00 +0100 Subject: [PATCH 4/4] Update versioned_docs/version-8.2/components/concepts/clusters.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- versioned_docs/version-8.2/components/concepts/clusters.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-8.2/components/concepts/clusters.md b/versioned_docs/version-8.2/components/concepts/clusters.md index a9b0c153138..c83b48d12a5 100644 --- a/versioned_docs/version-8.2/components/concepts/clusters.md +++ b/versioned_docs/version-8.2/components/concepts/clusters.md @@ -38,9 +38,8 @@ You can resume a paused cluster at any time, which typically takes five to ten m - Clusters tagged as `dev` (or untagged) auto-pause eight hours after the cluster is created or resumed from a paused state. - Clusters tagged as `test`, `stage`, or `prod` auto-pause if there is no cluster activity for 48 hours. - Cluster disk space is cleared when a trial cluster is paused. - - You will need to redeploy processes to the cluster once it is resumed from a paused state. - - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. - + - You will need to redeploy processes to the cluster once it is resumed from a paused state. + - Cluster configuration settings (for example, API Clients, Connector secrets, and IP allowlists) are saved so you can easily resume a cluster. :::tip To prevent auto-pause, [Upgrade your Free Trial plan](https://camunda.com/pricing/) to a Starter or Enterprise plan.