From 2d41b674a877c5d94bfe0bcbb211a4f87cc0ed90 Mon Sep 17 00:00:00 2001 From: Solomon Hykes Date: Thu, 7 Apr 2022 23:11:47 +0000 Subject: [PATCH] Docs: fix formatting in article 1221 Signed-off-by: Solomon Hykes --- docs/core-concepts/1221-action.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core-concepts/1221-action.md b/docs/core-concepts/1221-action.md index ed9affdd..a5366987 100644 --- a/docs/core-concepts/1221-action.md +++ b/docs/core-concepts/1221-action.md @@ -34,7 +34,7 @@ A composite action's lifecycle has 4 stages: 3. Discovery 4. Execution -## Definition +### Definition A new action is *defined* in a declarative template called a [CUE definition](https://cuetorials.com/overview/foundations/#definitions). This definition describes the action's inputs, outputs, sub-actions, and the wiring between them. @@ -76,7 +76,7 @@ Also note the free-form structure: an action definition is not structured by a r There are no constraints to an action's field names or types. -## Integration +### Integration Action definitions cannot be executed directly: they must be integrated into a plan. @@ -113,7 +113,7 @@ Note that `#AddHello` was integrated *directly* into the plan, whereas `core.#Wr To learn more about the structure of a plan, see [it all begins with a plan](./1202-plan). -## Discovery +### Discovery Once integrated into a plan, actions can be discovered by end users, by using the familiar convention of usage messages: @@ -131,7 +131,7 @@ Flags: [...] ``` -## Execution +### Execution Once the end user has discovered the action that they need, they can execute it with `dagger do`. For example: