Skip to content
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.

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

docs: update broken task file #757

Merged
merged 5 commits into from
Feb 6, 2023
Merged
Changes from all commits
Commits
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
7 changes: 4 additions & 3 deletions docs/content/en/docs/concepts/tasks/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,7 @@ spec:
console.log("Deployment Task has been executed");
```

In the code section, it is possible to define a full-fletched Deno script. An example for that would be:

In the code section, it is possible to define a full-fletched Deno script.
```yaml
apiVersion: lifecycle.keptn.sh/v1alpha2
kind: KeptnTaskDefinition
Expand Down Expand Up @@ -68,6 +67,8 @@ spec:
url: <url>
```

An example is available [here](https://github.com/keptn-sandbox/lifecycle-toolkit-examples/blob/main/sample-app/version-1/app-pre-deploy.yaml).

Finally, `KeptnTaskDefinition` can build on top of other `KeptnTaskDefinition`s.
This is a common use case where a general function can be re-used in multiple places with different parameters.

Expand Down Expand Up @@ -99,4 +100,4 @@ Here, the `secret` value is the K8s secret name that will be mounted into the ru

A Task is responsible for executing the TaskDefinition of a workload.
The execution is done spawning a K8s Job to handle a single Task.
In its state, it keeps track of the current status of the K8s Job created.
In its state, it keeps track of the current status of the K8s Job created.