fix(docs): fix some 404 links

kestra-io · Dec 29, 2024 · 58a98a0 · 58a98a0
1 parent f3a1135
commit 58a98a0
Show file tree

Hide file tree

Showing 6 changed files with 16 additions and 15 deletions.
diff --git a/content/docs/04.workflow-components/01.flow.md b/content/docs/04.workflow-components/01.flow.md
@@ -156,7 +156,7 @@ You can access old revisions inside the **Revisions** tab of the **Flows** page.
 
 ## Triggers
 
-[Triggers](./triggers) are a way to start a flow from external events. For example, a trigger might initiate a flow at a scheduled time or based on external events (webhooks, file creation, message in a broker, etc.).
+[Triggers](./07.triggers) are a way to start a flow from external events. For example, a trigger might initiate a flow at a scheduled time or based on external events (webhooks, file creation, message in a broker, etc.).
 
 ## Flow variable expressions
 

diff --git a/content/docs/04.workflow-components/01.tasks/02.scripts/00.languages.md b/content/docs/04.workflow-components/01.tasks/02.scripts/00.languages.md
@@ -285,6 +285,7 @@ tasks:
 This example can be found in the [Node.js docs](https://nodejs.org/en/learn/getting-started/nodejs-with-typescript#examples). We're going to save it as `example.ts`.
 
 ```typescript
+
 type User = {
   name: string;
   age: number;

diff --git a/content/docs/04.workflow-components/01.tasks/02.taskruns.md b/content/docs/04.workflow-components/01.tasks/02.taskruns.md
@@ -21,16 +21,16 @@ If retries have been configured, a task failure will generate new attempts until
 
 Similar to Executions, Task Runs cans be in a particular state.
 
-| State | Description                                                                                                                                                                                                                                  |
-| - |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `CREATED` | The Execution or Task Run is waiting to be processed. This state usually means that the Execution is in a queue and is yet to be started.                                                                                                |
-| `RUNNING` | The Execution or Task Run is currently being processed.                                                                                                                                                                                  |
-| `SUCCESS` | The Execution or Task Run has been completed successfully.                                                                                                                                                                               |
-| `WARNING` | The Execution or Task Run exhibited unintended behavior, but the execution continued and was flagged with a warning.                                                                                                                     |
+| State | Description                                                                                                                                                                                                                               |
+| - |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `CREATED` | The Execution or Task Run is waiting to be processed. This state usually means that the Execution is in a queue and is yet to be started.                                                                                                 |
+| `RUNNING` | The Execution or Task Run is currently being processed.                                                                                                                                                                                   |
+| `SUCCESS` | The Execution or Task Run has been completed successfully.                                                                                                                                                                                |
+| `WARNING` | The Execution or Task Run exhibited unintended behavior, but the execution continued and was flagged with a warning.                                                                                                                      |
 | `FAILED` | The Execution or Task Run exhibited unintended behavior that caused the execution to fail.                                                                                                                                                |
-| `RETRYING` | The Execution or Task Run is currently being [retried](./12.retries.md).                                                                                                                                                                |
-| `RETRIED` | An Execution or Task Run exhibited unintended behavior, stopped, and created a new execution as defined by its [flow-level retry policy](./12.retries.md#flow-level-retries). The policy was set to the `CREATE_NEW_EXECUTION` behavior. |
-| `KILLING` | A command was issued that asked for the Execution or Task Run to be killed. The system is in the process of killing the associated tasks.                                                                                                |
+| `RETRYING` | The Execution or Task Run is currently being [retried](../12.retries.md).                                                                                                                                                                 |
+| `RETRIED` | An Execution or Task Run exhibited unintended behavior, stopped, and created a new execution as defined by its [flow-level retry policy](../12.retries.md#flow-level-retries). The policy was set to the `CREATE_NEW_EXECUTION` behavior. |
+| `KILLING` | A command was issued that asked for the Execution or Task Run to be killed. The system is in the process of killing the associated tasks.                                                                                                 |
 | `KILLED` | An Execution or Task Run was killed (upon request), and no more tasks will run.                                                                                                                                                           |
 
 ::alert{type="info"}

diff --git a/content/docs/06.enterprise/07.namespace-management.md b/content/docs/06.enterprise/07.namespace-management.md
@@ -39,9 +39,9 @@ You can only filter for existing namespaces. Once you are ready to turn a placeh
 ## Namespace-level features: secrets, variables and plugin defaults
 
 Once you create a namespace, you can centrally govern the following:
-- [namespace-level secrets](/docs/concepts/secret)
-- [namespace-level variables](/docs/workflow-components/variables) which values can be accessed through `{{ namespace.my_variable_name }}`
-- [namespace-level plugin defaults](/docs/workflow-components/task-defaults).
+- [namespace-level secrets](../06.enterprise/secrets.md)
+- [namespace-level variables](../06.enterprise/07.namespace-management.md#namespace-level-features-secrets-variables-and-plugin-defaults) which values can be accessed through `{{ namespace.my_variable_name }}`
+- [namespace-level plugin defaults](../06.enterprise/08.centralized-task-configuration.md).
 
 Since Kestra supports [everything as code and from the UI](https://youtu.be/dU3p6Jf5fMw?si=bqNWS1e3_if-mePS), you can manage namespaces from the UI or programmatically (e.g. via our [Terraform provider](https://registry.terraform.io/providers/kestra-io/kestra/latest/docs)).
 

diff --git a/content/docs/plugin-developer-guide/02.task.md b/content/docs/plugin-developer-guide/02.task.md
@@ -393,7 +393,7 @@ Remember to document your tasks. For this, we provide a set of annotations expla
 
 ## Flowable Task
 
-[Flowable tasks](../workflow-components/tasks/00.flowable-tasks) are the most complex tasks to develop, and will usually be available from Kestra core. You will rarely need to create a flowable task by yourself.
+[Flowable tasks](../04.workflow-components/01.tasks/00.flowable-tasks.md) are the most complex tasks to develop, and will usually be available from Kestra core. You will rarely need to create a flowable task by yourself.
 
 ::alert{type="warning"}
 When developing such tasks, you must make it fault-tolerant as an exception thrown by a flowable task can endanger the Kestra instance and lead to inconsistencies in the flow execution.

diff --git a/content/docs/version-control-cicd/cicd/07.kubernetes-operator.md b/content/docs/version-control-cicd/cicd/07.kubernetes-operator.md
@@ -61,7 +61,7 @@ The Kestra Kubernetes operator will watch for three Kestra resources in all name
 
 - `KestraFlow`, shortname **flow**. To manage [flows](../../04.workflow-components/01.flow.md).
 - `KestraKeyValue`, shortnames **keyvalue** or **kv**. To manage [K/V store](../../05.concepts/05.kv-store.md) entries.
-- `KestraNamespaceFile`, shortnames **namespacefile** or **nsfile**. To manage [Namespace files](../../08.developer-guide/03.namespace-files.md).
+- `KestraNamespaceFile`, shortnames **namespacefile** or **nsfile**. To manage [Namespace files](../../05.concepts/02.namespace-files.md).
 
 ### Managing Flow resources