You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/stepactions.md
+29-3Lines changed: 29 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ A `StepAction` is the reusable and scriptable unit of work that is performed by
17
17
18
18
A `Step` is not reusable, the work it performs is reusable and referenceable. `Steps` are in-lined in the `Task` definition and either perform work directly or perform a `StepAction`. A `StepAction` cannot be run stand-alone (unlike a `TaskRun` or a `PipelineRun`). It has to be referenced by a `Step`. Another way to ehink about this is that a `Step` is not composed of `StepActions` (unlike a `Task` being composed of `Steps` and `Sidecars`). Instead, a `Step` is an actionable component, meaning that it has the ability to refer to a `StepAction`. The author of the `StepAction` must be able to compose a `Step` using a `StepAction` and provide all the necessary context (or orchestration) to it.
19
19
20
-
20
+
21
21
## Configuring a `StepAction`
22
22
23
23
A `StepAction` definition supports the following fields:
@@ -29,7 +29,7 @@ A `StepAction` definition supports the following fields:
29
29
-[`metadata`][kubernetes-overview] - Specifies metadata that uniquely identifies the
30
30
`StepAction` resource object. For example, a `name`.
31
31
-[`spec`][kubernetes-overview] - Specifies the configuration information for this `StepAction` resource object.
32
-
-`image` - Specifies the image to use for the `Step`.
32
+
-`image` - Specifies the image to use for the `Step`.
33
33
- The container image must abide by the [container contract](./container-contract.md).
34
34
- Optional
35
35
-`command`
@@ -50,7 +50,7 @@ spec:
50
50
env:
51
51
- name: HOME
52
52
value: /home
53
-
image: ubuntu
53
+
image: ubuntu
54
54
command: ["ls"]
55
55
args: ["-lh"]
56
56
```
@@ -169,3 +169,29 @@ spec:
169
169
timeout: 1h
170
170
onError: continue
171
171
```
172
+
173
+
### Specifying Remote StepActions
174
+
175
+
A `ref` field may specify a StepAction in a remote location such as git.
176
+
Support for specific types of remote will depend on the Resolvers your
177
+
cluster's operator has installed. For more information including a tutorial, please check [resolution docs](resolution.md). The below example demonstrates referencing a StepAction in git:
0 commit comments