Replies: 6 comments
-
This point is excellent, and it's what we want tbh. There are several things which be listed in our roadmap already, but I didn't have time to start until today. 😓 Please join our next public community MTG for further discussion. And let's list up idea under this discussion 👍 |
Beta Was this translation helpful? Give feedback.
-
discussion in 2023/10/27 Notefrom @sivchari
from @khanhtc1202
memos
Next Action
|
Beta Was this translation helpful? Give feedback.
-
Plugin over gRPC: https://github.com/hashicorp/go-plugin |
Beta Was this translation helpful? Give feedback.
-
About the plan, it would be better to keep the first version of pluggable piped separated from the piped source. So that we can keep develop new features for piped while refactoring the piped architect to make it pluggable. => Let's create: /pkg/app/pipedv1 as copy of /pkg/app/piped |
Beta Was this translation helpful? Give feedback.
-
What to concern?
|
Beta Was this translation helpful? Give feedback.
-
We will track the process via this issue 👍 |
Beta Was this translation helpful? Give feedback.
-
I propose custom platform provider. Now, PipeCD can only manage Kubernetes/CloudRun/ECS/Lambda/Terraform.
But other than that, PipeCD can't manage. If we define specification to extend manage resources, developers can use PipeCD for many resources. wdyt ?
Beta Was this translation helpful? Give feedback.
All reactions