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
* Source image name from local yaml file
Signed-off-by: Tom Fay <[email protected]>
* Remove stray comment
Signed-off-by: Tom Fay <[email protected]>
* Correct key in doc
Signed-off-by: Tom Fay <[email protected]>
* Fix case where floki is run from a subdirectory
Signed-off-by: Tom Fay <[email protected]>
* Change error message
Signed-off-by: Tom Fay <[email protected]>
Copy file name to clipboardExpand all lines: docs/content/intro/feature-overview.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ The ideal workflow is
16
16
17
17
# Container images
18
18
19
-
`floki` offers a couple of ways t configure the container image to use.
19
+
`floki` offers a couple of ways to configure the container image to use.
20
20
21
21
## Prebuilt images
22
22
@@ -40,6 +40,16 @@ image:
40
40
context: . # Defaults to .
41
41
```
42
42
43
+
## Referencing a key in another yaml file
44
+
`floki` can use an image referenced in another yaml file. This can help keep local development environments sync'd with a CI environment.
45
+
46
+
```
47
+
image:
48
+
yaml:
49
+
file: .gitlab-ci.yaml
50
+
key: variables.RUST-IMAGE
51
+
```
52
+
43
53
## Updating an image
44
54
45
55
`floki pull` pulls the container under the `image` key again. While it is better to version images, this can be used when working against e.g. a `latest` tag.
0 commit comments