From 0461958a9ecb1186a36165e60faa85fd3ded9ed0 Mon Sep 17 00:00:00 2001 From: Jake Cohen Date: Mon, 12 May 2025 08:38:10 -0700 Subject: [PATCH] add note about restriction to self-hosted --- docs/administration/runner/runner-plugins/custom-plugins.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/administration/runner/runner-plugins/custom-plugins.md b/docs/administration/runner/runner-plugins/custom-plugins.md index f4a1a1109..2f78913fb 100644 --- a/docs/administration/runner/runner-plugins/custom-plugins.md +++ b/docs/administration/runner/runner-plugins/custom-plugins.md @@ -11,6 +11,10 @@ Enterprise Runners allow remote execution and workflow orchestration close to ta The installation process varies depending on how the Runner is deployed: on a virtual machine, in a Docker container, or in Kubernetes. This article provides clear instructions for each deployment model. +:::warning Only Available on Runbook Automation Self-Hosted +The custom plugin feature is only available on the self-hosted version of Runbook Automation. It is not available on the cloud version. +::: + ## Prerequisites 1. In order for the plugin to be configurable in the GUI, the plugin must also be uploaded to the server. This can be done through the GUI ([example](/learning/howto/how2kube.md#installing-the-kubernetes-plugin-in-rundeck)) or manually [copying the plugin artifacts](/administration/configuration/plugins/installing.md) to the plugins directory.