Init alpha usage of pipedv1 and plugins#5878
Conversation
Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5878 +/- ##
=======================================
Coverage 27.85% 27.85%
=======================================
Files 519 519
Lines 55793 55793
=======================================
Hits 15539 15539
Misses 39070 39070
Partials 1184 1184
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| # Usage of pipedv1 and plugins (alpha) | ||
|
|
||
| This page shows how to run pipedv1 and plugins of alpha status. | ||
|
|
There was a problem hiding this comment.
[imo] it would be nice to clarify that this doc is WIP for now.
|
@t-kikuc Nice work. My only concern is the name of the docs. I think renaming it to README.md is fine. The title of the docs speaks for itself already; there is no need to make the name |
|
That's because README.md already exists.
How about moving or renaming after finding a better place? |
|
@t-kikuc got that. Thank you! |
| 2. Run pipedv1 | ||
|
|
||
| ```sh | ||
| docker run pipe-cd/pipecd/pipedv1:v0.52.0 piped --config-file=/path/to/piped-config.yaml --tools-dir=/tmp/piped-bin |
There was a problem hiding this comment.
TODO: use binary instead of docker for now
What this PR does:
as title
Why we need it:
Early users can try pipedv1 and plugins.
Which issue(s) this PR fixes:
Part of #5615
Note
TODO :
app.pipecd.yaml: k8s stages inpipelineandplugins.kubernetes