From e08ce14981ceedf602aa2045c04573b10ce7bf1f Mon Sep 17 00:00:00 2001 From: Scott Date: Thu, 25 Mar 2021 06:31:17 -0400 Subject: [PATCH] Remove mention of absolute vs relative path from workspaces doc Similarly to commit d80cbc our workspace docs stated that if you provide a relative path to the workspace's `mountPath` then it would be appended to `/workspace`. This was never the case and so this commit removes mention of it. --- docs/workspaces.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/workspaces.md b/docs/workspaces.md index 242c36d60ce..6e91e6c6512 100644 --- a/docs/workspaces.md +++ b/docs/workspaces.md @@ -110,10 +110,6 @@ Note the following: **at most** one _writeable_ `Workspace`. - A `readOnly` `Workspace` will have its volume mounted as read-only. Attempting to write to a `readOnly` `Workspace` will result in errors and failed `TaskRuns`. -- `mountPath` can be either absolute or relative. Absolute paths start with `/` and relative paths - start with the name of a directory. For example, a `mountPath` of `"/foobar"` is absolute and exposes - the `Workspace` at `/foobar` inside the `Task's` `Steps`, but a `mountPath` of `"foobar"` is relative and - exposes the `Workspace` at `/workspace/foobar`. Below is an example `Task` definition that includes a `Workspace` called `messages` to which the `Task` writes a message: