From 37b73a0c0e52efc3a6f38c5a8e3ce74dd3af8962 Mon Sep 17 00:00:00 2001 From: Matthew Casperson Date: Fri, 22 Dec 2023 12:22:47 +1100 Subject: [PATCH] Linked to example video (#2131) --- .../docs/platform-engineering/managing-runbook-resources.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/pages/docs/platform-engineering/managing-runbook-resources.md b/src/pages/docs/platform-engineering/managing-runbook-resources.md index e847f24be2..b0d5a3511e 100644 --- a/src/pages/docs/platform-engineering/managing-runbook-resources.md +++ b/src/pages/docs/platform-engineering/managing-runbook-resources.md @@ -7,6 +7,8 @@ description: This section documents how to manage runbooks as code. navOrder: 6 --- +[Serializing and deploying runbook resources](https://www.youtube.com/watch?v=mPBeqOwkY4Q) + [Runbooks](/docs/runbooks) are a component of a project, sharing or referencing much of the project's configuration such as variables, connected library variable sets, tenants, and lifecycles. However, it can be useful to treat runbooks as an independently deployable artifact. This allows a common runbook to be shared across many projects.