From 52ccff3efcebee04e58874e17e11f91601e31d35 Mon Sep 17 00:00:00 2001 From: Mikhail Astashkevich Date: Fri, 15 Nov 2024 13:06:28 +0100 Subject: [PATCH 1/3] docs: Update Staging Environments docs --- docs/pages/product/workspace/environments.mdx | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docs/pages/product/workspace/environments.mdx b/docs/pages/product/workspace/environments.mdx index a5fe797a63455..1ccca56f8d8c2 100644 --- a/docs/pages/product/workspace/environments.mdx +++ b/docs/pages/product/workspace/environments.mdx @@ -12,9 +12,18 @@ An environment provides access to your data model. Cube Cloud provides the follo You cannot query the development enviornment unless your user is in dev mode on the branch you are trying to access. ## Staging Environments -Staging environments are typically only available when the linked branch is active. -An active branch is the one that is selected on the Data Model screen by at least one user. -To keep a staging environment always active, toggle the switch for the corresponding branch in Settings > Staging Environments. +Staging environments are created for each branch in your repository. By default, these environments are only accessible when the branch is actively being viewed on the Data Model screen by at least one user. When no users are viewing the branch, the environment becomes inactive and its resources are deallocated. + +To maintain continuous access to a staging environment regardless of user activity, you can use the "Always Active" toggle in Settings > Staging Environments. Here's how it works: + +- Toggle OFF (default): The environment is only accessible when users are actively viewing the branch. When no users are viewing the branch, queries to this environment will fail. +- Toggle ON: The environment remains active and accessible 24/7, regardless of user activity. + +### Cost Implications +Please note that staging environments consume resources only when they are being actively used: +- Environments automatically suspend after 10 minutes of inactivity, regardless of the "Always Active" toggle setting +- You are only charged for the time when environments are actively being used + Date: Fri, 15 Nov 2024 13:21:27 +0100 Subject: [PATCH 2/3] fix --- docs/pages/product/workspace/environments.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/pages/product/workspace/environments.mdx b/docs/pages/product/workspace/environments.mdx index 1ccca56f8d8c2..7780d1c821cac 100644 --- a/docs/pages/product/workspace/environments.mdx +++ b/docs/pages/product/workspace/environments.mdx @@ -12,17 +12,18 @@ An environment provides access to your data model. Cube Cloud provides the follo You cannot query the development enviornment unless your user is in dev mode on the branch you are trying to access. ## Staging Environments -Staging environments are created for each branch in your repository. By default, these environments are only accessible when the branch is actively being viewed on the Data Model screen by at least one user. When no users are viewing the branch, the environment becomes inactive and its resources are deallocated. +Staging environments are created for each branch in your repository. By default, these environments are only accessible when the branch is being viewed on the Data Model screen by at least one user. When no users are viewing the branch, the environment becomes inactive and inaccessible. To maintain continuous access to a staging environment regardless of user activity, you can use the "Always Active" toggle in Settings > Staging Environments. Here's how it works: -- Toggle OFF (default): The environment is only accessible when users are actively viewing the branch. When no users are viewing the branch, queries to this environment will fail. +- Toggle OFF (default): The environment is only accessible when users are viewing the branch. When no users are viewing the branch, queries to this environment will fail. - Toggle ON: The environment remains active and accessible 24/7, regardless of user activity. ### Cost Implications -Please note that staging environments consume resources only when they are being actively used: +Please note that staging environments consume resources only when they are being used: - Environments automatically suspend after 10 minutes of inactivity, regardless of the "Always Active" toggle setting -- You are only charged for the time when environments are actively being used +- You are only charged for the time when environments are being used +Therefore, the "Always Active" toggle only affects accessibility to inactive branches and does not impact your costs directly. Date: Fri, 15 Nov 2024 13:43:35 +0100 Subject: [PATCH 3/3] fix --- docs/pages/product/workspace/environments.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/pages/product/workspace/environments.mdx b/docs/pages/product/workspace/environments.mdx index 7780d1c821cac..edc67d805a3ce 100644 --- a/docs/pages/product/workspace/environments.mdx +++ b/docs/pages/product/workspace/environments.mdx @@ -23,6 +23,7 @@ To maintain continuous access to a staging environment regardless of user activi Please note that staging environments consume resources only when they are being used: - Environments automatically suspend after 10 minutes of inactivity, regardless of the "Always Active" toggle setting - You are only charged for the time when environments are being used + Therefore, the "Always Active" toggle only affects accessibility to inactive branches and does not impact your costs directly.