Skip to content

fix typo in migration guides #6374

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

Merged
khanhtc1202 merged 1 commit into from
Dec 9, 2025
Merged

fix typo in migration guides #6374

Show file tree
Hide file tree
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
8 changes: 5 additions & 3 deletions docs/content/en/docs-dev/migrating-from-v0-to-v1/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
---
title: "Migrating to PipeCD V1"
linkTitle: "Migrating to PipeCD V1"
title: "Migrate to PipeCD V1"
linkTitle: "Migrate to PipeCD V1"
weight: 90
description: >
Documentation on migrating your application from PipeCD V0 to V1
---

This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD.

Incase you are using PipeCD V0, follow the setps on this page to migrate to **PipeCD V1**.

## Overview

PipeCD V1 introduces a **pluggable architecture** that allows developers to add and maintain custom deployment and operational plugins without modifying the core system of PipeCD.
Expand Down Expand Up @@ -97,7 +99,7 @@ Or specify an entire directory:
pipectl migrate application-config --dirs=path/to/apps/
```

Here is an example for a simple app.pipecd.yaml file which demonstrates a Kubernetes deployment and simulates a 30s wait:
Here is an example for a simple app.pipecd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:

```yaml
apiVersion: pipecd.dev/v1beta1
Expand Down
6 changes: 3 additions & 3 deletions docs/content/en/docs-v1.0.x/migrating-from-v0-to-v1/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: >
Documentation on migrating your application from PipeCD V0 to V1
---

This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD.
This page explains how to safely migrate your existing PipeCD System to the RC version of **PipeCD V1**, the new plugin-based architecture that brings modularity and extensibility to PipeCD.

Incase you are using PipeCD V0, follow the setps on this page to migrate to **PipeCD V1**.

Expand Down Expand Up @@ -99,7 +99,7 @@ Or specify an entire directory:
pipectl migrate application-config --dirs=path/to/apps/
```

Here is an example for a simple app.pippcd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:
Here is an example for a simple app.pipecd.yaml file which demonstrates a kubernetes deployment and simulates a 30s wait:

```yaml
apiVersion: pipecd.dev/v1beta1
Expand Down Expand Up @@ -300,4 +300,4 @@ Simply **stop** the running `pipedv1` instance, then **start** the `pipedv0` ser

Once restarted, the old `pipedv0` should resume operation using its previous configuration and state. Happy Pipe-CDing!

---
---