From 50873ff98d8fd2bcbda9c9c6cca479f0921c6c77 Mon Sep 17 00:00:00 2001 From: Tanu Date: Fri, 1 May 2026 15:34:19 +0530 Subject: [PATCH] Update configuring-a-plugin.md Signed-off-by: Tanu Signed-off-by: tanupriyasingh1 --- .../user-guide/managing-piped/configuring-a-plugin.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md b/docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md index 9f4432affa..3ca85b13e0 100644 --- a/docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md +++ b/docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md @@ -19,10 +19,9 @@ Currently, the official plugins maintained by the PipeCD Maintainers are: - Wait - Wait Approval -We are working towards releasing more plugins in the future. +We are working towards releasing more plugins in the future. You can track progress and find community-maintained plugins like ECS and Lambda in the [community-plugins repository](https://github.com/pipe-cd/community-plugins). + ->**Note:** -> We also have the [PipeCD Community Plugins repository](https://github.com/pipe-cd/community-plugins) for plugins made by the PipeCD Community. A plugin is added to the piped configuration inside the `spec.plugins` array and providing the plugin’s executable URL, the port it should run on, and any deploy targets that belong to it. For more details, see the [configuration reference for plugins](../configuration-reference/#plugins).