From 8216ab6c578e8fa4ff64195f5c0526665baf8e64 Mon Sep 17 00:00:00 2001 From: Ajay Kidave Date: Fri, 1 Nov 2024 17:18:05 -0700 Subject: [PATCH] Clarify external plugin status --- content/docs/Plugins/Overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/Plugins/Overview.md b/content/docs/Plugins/Overview.md index 11f09d3..9560663 100644 --- a/content/docs/Plugins/Overview.md +++ b/content/docs/Plugins/Overview.md @@ -7,7 +7,7 @@ summary: "Overview of how plugins work, how to use them" Plugins provide an API for Clace Starlark code to call out to external systems. Plugins are implemented in Go. Every plugin API calls needs to be in the approved list for it to be permitted. See [security]({{< ref "appsecurity#sample-application" >}}/) for an overview of the security model. -Each plugin is identified by a unique name, like `store.in` or `exec.in`. Plugins ending with `.in` are internal plugins, built into the Clace binary. Support for external plugins which are loaded dynamically is currently in progress. +Each plugin is identified by a unique name, like `store.in` or `exec.in`. Plugins ending with `.in` are internal plugins, built into the Clace binary. Support for external plugins which are loaded dynamically is planned. ## Plugin Usage