-
Notifications
You must be signed in to change notification settings - Fork 154
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.
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
Add docs and example config for local development #4477
Add docs and example config for local development #4477
Conversation
Signed-off-by: Kenta Kozuka <[email protected]>
Signed-off-by: Kenta Kozuka <[email protected]>
cmd/piped/README.md
Outdated
|
||
## How to add an application to PipeCD | ||
|
||
1. Access the console, go Application page and click `ADD` button, select a platform provider and application(e.g. `name: simple, repo example` if you use the example repository). Then, click `SAVE`. PipeCD automatically will run its deployment. | ||
|
||
2. You can see the deployment running on the Deployment list page on the console. When the deployment is done, you can check the application running in your cluster; | ||
|
||
``` console | ||
> kubectl get pods | ||
NAME READY STATUS RESTARTS AGE | ||
simple-6b47c4c69b-9fmgg 1/1 Running 0 3m6s | ||
simple-6b47c4c69b-qzpj8 1/1 Running 0 3m6s | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not development docs for piped, I think we can remove this 🤔
cmd/piped/README.md
Outdated
|
||
## How to run Piped agent locally | ||
|
||
1. Prepare the piped configuration file `piped-config.yaml` | ||
1. Prepare the piped configuration file `piped-config.yaml`. You can find an example config [here](https://github.com/pipe-cd/pipecd/tree/master/cmd/piped/example/piped-config.yaml). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Directly placing piped-config.yaml
file here could be better, readers can focus on the docs, not jumping around 😄
Signed-off-by: Kenta Kozuka <[email protected]>
@khanhtc1202 Fixed 👍 |
cmd/piped/README.md
Outdated
|
||
## How to run Piped agent locally | ||
|
||
1. Prepare the piped configuration file `piped-config.yaml` | ||
1. Prepare the piped configuration file `piped-config.yaml`. You can find an example config [here](https://github.com/pipe-cd/pipecd/tree/master/cmd/piped/piped-config.yaml). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kentakozuka Sorry, I mean, lets add the content of the example piped-config.yaml
file in this file instead of making it a separate file 🙏
Signed-off-by: Kenta Kozuka <[email protected]>
Signed-off-by: Kenta Kozuka <[email protected]>
@khanhtc1202 Fixed 👍 |
config: | ||
# FIXME: Replace here with your kubeconfig absolute file path. | ||
kubeConfigPath: /path/to/.kube/config | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@khanhtc1202 Is this what you meant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is 👍
apiVersion: pipecd.dev/v1beta1 | ||
kind: Piped | ||
spec: | ||
projectID: quickstart |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
projectID: quickstart | |
# Replace with the project used when registering for piped ID/Key. | |
projectID: quickstart |
Signed-off-by: Kenta Kozuka <[email protected]>
@khanhtc1202 Fixed 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you 🫡
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #4476
Does this PR introduce a user-facing change?: