Skip to content

docs: improve configuring-a-plugin page clarity and add community plugins link #6731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tanupriyasingh1 wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −3
Open

docs: improve configuring-a-plugin page clarity and add community plugins link #6731

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/content/en/docs-v1.0.x/user-guide/managing-piped/configuring-a-plugin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down
Loading