From fba83d835f91a9736a39ccdd728eecf58cc7ea26 Mon Sep 17 00:00:00 2001 From: Will Russell Date: Fri, 13 Dec 2024 21:27:00 +0000 Subject: [PATCH] feat(docs): december videos --- content/blogs/release-0-20.md | 2 +- content/docs/04.workflow-components/18.sla.md | 4 ++++ content/docs/05.concepts/11.storage.md | 6 ++++++ .../docs/15.how-to-guides/namespace-variables-vs-kvstore.md | 6 +++++- content/docs/15.how-to-guides/null-values.md | 6 ++++++ content/docs/15.how-to-guides/parallel-vs-sequential.md | 4 ++++ 6 files changed, 26 insertions(+), 2 deletions(-) diff --git a/content/blogs/release-0-20.md b/content/blogs/release-0-20.md index 500e3b80e5..5a010d00e4 100644 --- a/content/blogs/release-0-20.md +++ b/content/blogs/release-0-20.md @@ -23,7 +23,7 @@ The table below highlights the key features of this release. | Team-level Storage and Secret Backends Isolation | Provide data isolation across business units or teams by configuring dedicated storage or secret backends for each tenant or namespace. | Enterprise Edition | | Invitations | Add new users to your tenant or instance by using the [invitation process](https://kestra.io/docs/enterprise/invitations). | Enterprise Edition | | Announcements | [Add a custom announcement](https://kestra.io/docs/enterprise/announcements) to inform users about planned maintenance downtimes, outages, or incidents. | Enterprise Edition | -| Flow-level SLA (Beta) | [Set custom SLA](https://kestra.io/docs/workflow-components/sla) conditions for each workflow using the new `sla` property of a flow. | All editions | +| Flow-level SLA (Beta) | [Set custom SLA](https://youtu.be/FlkyPIWPLSk) conditions for each workflow using the new `sla` property of a flow. | All editions | | New core `runIf` task property | [Skip a task](https://youtu.be/Wc1mfa1SK60) if the provided condition evaluates to false. | All editions | | System Labels | [Prevent edits](https://kestra.io/docs/concepts/system-labels) from the UI with `system.readOnly` label and track cross-execution dependencies with `system.correlationId` label. | All editions | | Flow Trigger enhancements | Configure complex dependencies, e.g., when a flow relies on multiple other flows to finish by a certain deadline. | All editions | diff --git a/content/docs/04.workflow-components/18.sla.md b/content/docs/04.workflow-components/18.sla.md index 76ca0b9c31..e47f787b67 100644 --- a/content/docs/04.workflow-components/18.sla.md +++ b/content/docs/04.workflow-components/18.sla.md @@ -7,6 +7,10 @@ editions: ["Beta"] Assert that your workflows meet SLAs. +
+ +
+ ## What is an SLA An SLA (Service Level Agreement) is a core property of a flow that defines a `behavior` that should be triggered if the flow runs for too long or doesn't satisfy the assertion defined in the SLA. diff --git a/content/docs/05.concepts/11.storage.md b/content/docs/05.concepts/11.storage.md index a0118149bb..b1a0e04096 100644 --- a/content/docs/05.concepts/11.storage.md +++ b/content/docs/05.concepts/11.storage.md @@ -304,6 +304,12 @@ The script can access a logger to log messages. Each row is available in a `row` ## Purging data +
+ +
+ +--- + The [PurgeExecution](/plugins/core/tasks/storages/io.kestra.plugin.core.storage.Purgeexecution) task can purge all the files stored inside the internal context by a flow execution. It can be used at the end of a flow to purge all its generated files. diff --git a/content/docs/15.how-to-guides/namespace-variables-vs-kvstore.md b/content/docs/15.how-to-guides/namespace-variables-vs-kvstore.md index 859b7738d9..c276fbec92 100644 --- a/content/docs/15.how-to-guides/namespace-variables-vs-kvstore.md +++ b/content/docs/15.how-to-guides/namespace-variables-vs-kvstore.md @@ -1,5 +1,5 @@ --- -title: Namespace Variables vs. KV Store +title: Namespace Variables vs KV Store icon: /docs/icons/tutorial.svg stage: Getting Started topics: @@ -8,6 +8,10 @@ topics: When to store key-value pairs as namespace-level Variables vs. KV store +
+ +
+ + + +--- + The null coalescing operator is a binary operator that returns its left-hand value if it's not null; otherwise, it returns its right-hand value. You can think of it as a way to provide a default value when the left-hand value is null. ```yaml diff --git a/content/docs/15.how-to-guides/parallel-vs-sequential.md b/content/docs/15.how-to-guides/parallel-vs-sequential.md index 8adad7518c..53e2c4e800 100644 --- a/content/docs/15.how-to-guides/parallel-vs-sequential.md +++ b/content/docs/15.how-to-guides/parallel-vs-sequential.md @@ -8,6 +8,10 @@ topics: When to use parallel tasks and when to use sequential tasks in Kestra. +
+ +
+ ## Parallel Tasks The following flow has 6 tasks wrapped in the `Parallel` task. Since the `concurrent` property is set to 3, Kestra will run 3 tasks in parallel. As soon as any of the three tasks completes, the next task will start.