Skip to content

Commit 50873ff

Browse files
Update configuring-a-plugin.md
Signed-off-by: Tanu <tanuwu101@gmail.com> Signed-off-by: tanupriyasingh1 <tanuwu101@gmail.com>
1 parent a3fa0e0 commit 50873ff

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,9 @@ Currently, the official plugins maintained by the PipeCD Maintainers are:
1919
- Wait
2020
- Wait Approval
2121

22-
We are working towards releasing more plugins in the future.
22+
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).
23+
2324

24-
>**Note:**
25-
> We also have the [PipeCD Community Plugins repository](https://github.com/pipe-cd/community-plugins) for plugins made by the PipeCD Community.
2625

2726
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).
2827

0 commit comments

Comments
 (0)