From 60d059b6693041ec8ec3f54bd36af6554c5460e7 Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Fri, 15 Nov 2024 13:57:28 +0100 Subject: [PATCH 1/6] feat(concepts): suspend free trial - disk deletion on suspension - explanation whats retained & to be done if it occurs --- docs/components/concepts/clusters.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 530ea5570de..6c42f488d5a 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -78,6 +78,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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. +- Disk space will be cleared when a trial cluster is suspended. + - Cluster settings such as API Clients, connector secrets and IP-Whitelist are retained. + - Processes will need to be redeployed to the cluster. :::tip To prevent auto-pause, [upgrade your Free Trial plan](https://camunda.com/pricing/) to a Starter or Enterprise plan. From c6dde9a53a276edaf0eb16090443bba2b44796cd Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Fri, 15 Nov 2024 14:39:58 +0100 Subject: [PATCH 2/6] fix(docs): correct terminology --- docs/components/concepts/clusters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 6c42f488d5a..21d92ef650c 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -78,7 +78,7 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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. -- Disk space will be cleared when a trial cluster is suspended. +- Disk space will be cleared when a trial cluster is paused. - Cluster settings such as API Clients, connector secrets and IP-Whitelist are retained. - Processes will need to be redeployed to the cluster. From 3be474056cdc12b568c3ab58ad224dcd8ebc02a8 Mon Sep 17 00:00:00 2001 From: Simon Zengerling Date: Fri, 15 Nov 2024 14:58:54 +0100 Subject: [PATCH 3/6] fix(docs): correct terminology --- docs/components/concepts/clusters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 21d92ef650c..4f1be53af5c 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -78,7 +78,7 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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. -- Disk space will be cleared when a trial cluster is paused. +- Disk space will be cleared when a trial cluster is paused. - Cluster settings such as API Clients, connector secrets and IP-Whitelist are retained. - Processes will need to be redeployed to the cluster. From f3beb5321730408f2d63d66db0af00540e077f69 Mon Sep 17 00:00:00 2001 From: mesellings Date: Mon, 18 Nov 2024 15:51:36 +0000 Subject: [PATCH 4/6] TW edits --- docs/components/concepts/clusters.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/components/concepts/clusters.md b/docs/components/concepts/clusters.md index 4f1be53af5c..59408dc166f 100644 --- a/docs/components/concepts/clusters.md +++ b/docs/components/concepts/clusters.md @@ -78,9 +78,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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. -- Disk space will be cleared when a trial cluster is paused. - - Cluster settings such as API Clients, connector secrets and IP-Whitelist are retained. - - Processes will need to be redeployed to 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. From 11620d1335d64e2650116e9613e089f1d0a7085c Mon Sep 17 00:00:00 2001 From: mesellings Date: Mon, 18 Nov 2024 16:06:26 +0000 Subject: [PATCH 5/6] Backport changes --- versioned_docs/version-8.2/components/concepts/clusters.md | 3 +++ versioned_docs/version-8.3/components/concepts/clusters.md | 3 +++ versioned_docs/version-8.4/components/concepts/clusters.md | 3 +++ versioned_docs/version-8.5/components/concepts/clusters.md | 3 +++ versioned_docs/version-8.6/components/concepts/clusters.md | 3 +++ 5 files changed, 15 insertions(+) diff --git a/versioned_docs/version-8.2/components/concepts/clusters.md b/versioned_docs/version-8.2/components/concepts/clusters.md index 7d96ec32d5e..3ba5516408c 100644 --- a/versioned_docs/version-8.2/components/concepts/clusters.md +++ b/versioned_docs/version-8.2/components/concepts/clusters.md @@ -39,6 +39,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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.3/components/concepts/clusters.md b/versioned_docs/version-8.3/components/concepts/clusters.md index f9544b7e507..f0348b30820 100644 --- a/versioned_docs/version-8.3/components/concepts/clusters.md +++ b/versioned_docs/version-8.3/components/concepts/clusters.md @@ -40,6 +40,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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.4/components/concepts/clusters.md b/versioned_docs/version-8.4/components/concepts/clusters.md index 051205775ec..db4bad1a4af 100644 --- a/versioned_docs/version-8.4/components/concepts/clusters.md +++ b/versioned_docs/version-8.4/components/concepts/clusters.md @@ -40,6 +40,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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.5/components/concepts/clusters.md b/versioned_docs/version-8.5/components/concepts/clusters.md index 255820f4532..bef1699122d 100644 --- a/versioned_docs/version-8.5/components/concepts/clusters.md +++ b/versioned_docs/version-8.5/components/concepts/clusters.md @@ -40,6 +40,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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 4a089f5bf05..b54b14f348f 100644 --- a/versioned_docs/version-8.6/components/concepts/clusters.md +++ b/versioned_docs/version-8.6/components/concepts/clusters.md @@ -78,6 +78,9 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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. From 144f06f4f2fcb207fc9855ed001849438a0ef55e Mon Sep 17 00:00:00 2001 From: mesellings Date: Tue, 19 Nov 2024 13:41:16 +0000 Subject: [PATCH 6/6] Remove 8.2 changes --- versioned_docs/version-8.2/components/concepts/clusters.md | 3 --- 1 file changed, 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 3ba5516408c..7d96ec32d5e 100644 --- a/versioned_docs/version-8.2/components/concepts/clusters.md +++ b/versioned_docs/version-8.2/components/concepts/clusters.md @@ -39,9 +39,6 @@ You can resume a paused cluster at any time, which typically takes five to ten m - 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.