Skip to content

Commit 970072f

Browse files
authored
chore(docs): add example scenario for parameter updates (coder#9298)
1 parent 52ea233 commit 970072f

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/templates/parameters.md

+15
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,21 @@ It prevents workspace users from becoming trapped with outdated template
118118
versions, ensuring they can smoothly update their workspace without any
119119
hindrances.
120120

121+
Example:
122+
123+
- Bob creates a workspace using the `python-dev` template. This template has a
124+
parameter `image_tag`, and Bob selects `1.12`.
125+
- Later, the template author Alice is notified of a critical vulnerability in a
126+
package installed in the `python-dev` template, which affects the image tag
127+
`1.12`.
128+
- Alice remediates this vulnerability, and pushes an updated template version
129+
that replaces option `1.12` with `1.13` for the `image_tag` parameter. She
130+
then notifies all users of that template to update their workspace
131+
immediately.
132+
- Bob saves their work, and selects the `Update` option in the UI. As their
133+
workspace uses the now-invalid option `1.12`, for the `image_tag` parameter,
134+
they are prompted to select a new value for `image_tag`.
135+
121136
## Required and optional parameters
122137

123138
A parameter is considered to be _required_ if it doesn't have the `default`

0 commit comments

Comments
 (0)