From cec706a8acc426859090842fc0983b5c75770a6b Mon Sep 17 00:00:00 2001 From: FogDong Date: Tue, 28 Jun 2022 17:03:14 +0800 Subject: [PATCH] fix broken link Signed-off-by: FogDong --- docs/end-user/workflow/overview.md | 3 +-- .../current/end-user/workflow/overview.md | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/end-user/workflow/overview.md b/docs/end-user/workflow/overview.md index 84c11669..a961c683 100644 --- a/docs/end-user/workflow/overview.md +++ b/docs/end-user/workflow/overview.md @@ -12,7 +12,7 @@ A workflow consists of multiple steps, and typical workflow steps include step g In fact, if you only use components in the Application and do not declare a workflow, KubeVela will automatically create a default workflow for deploying the components when running the Application. -In [VelaUX](../../how-to/dashboard/workflow/overview), you can feel the workflow more intuitively. As shown in the figure: The following is a workflow that controls the application to be deployed to the test environment, paused in the manual approval step, and then deployed to the production environment: +In VelaUX, you can feel the workflow more intuitively. As shown in the figure: The following is a workflow that controls the application to be deployed to the test environment, paused in the manual approval step, and then deployed to the production environment: ![continue-workflow](../../resources/continue-workflow.png) @@ -20,7 +20,6 @@ In [VelaUX](../../how-to/dashboard/workflow/overview), you can feel the workflow In the workflow, all the steps will be executed sequentially and the next step will be executed after the previous one succeeded. If a step is of type `step-group`, it can contain a series of sub-steps, all of which are executed together when the step group is executed. -> 在 KubeVela 未来的版本（1.5+）中，你可以显示地指定步骤的执行方式来控制并发或者单步执行，如： > In future versions of KubeVela (1.5+), you can explicitly specify the execution mode of steps, such as: > ```yaml > workflow: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/end-user/workflow/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/end-user/workflow/overview.md index 69461e30..7b154c2e 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/end-user/workflow/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/end-user/workflow/overview.md @@ -10,7 +10,7 @@ title: 工作流总览 实际上，如果你在应用部署计划中只使用了组件，并没有声明工作流时，KubeVela 会在运行这个应用时自动创建一个默认的工作流，用于部署应用中的组件。 -在 [VelaUX](../../how-to/dashboard/workflow/overview) 中，你可以更加直观地感受工作流。如图：下面是一个控制应用先部署到测试环境，暂停在人工审核步骤，然后再部署到生产环境的工作流： +在 VelaUX 中，你可以更加直观地感受工作流。如图：下面是一个控制应用先部署到测试环境，暂停在人工审核步骤，然后再部署到生产环境的工作流： ![continue-workflow](../../resources/continue-workflow.png)