Skip to content

Commit 0c32b5d

Browse files
committed
yaml: mark "Env" experimental for now
The syntax and the behavior of this field is still under discussion (PR 200), so this field is treated as experimental in the next upcoming release (v0.6.3). Probably we can move this out of experimental in v0.6.4. Signed-off-by: Akihiro Suda <[email protected]>
1 parent f8f3659 commit 0c32b5d

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

pkg/limayaml/default.yaml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,10 @@ network:
165165
# hostPortRange: [1024, 65535]
166166
# # Any port still not matched by a rule will not be forwarded (ignored)
167167

168-
# # extra environment variables that will be loaded into the VM at start up
168+
# Extra environment variables that will be loaded into the VM at start up.
169+
# These variables are currently only consumed by internal init scripts, not by the user shell.
170+
# This field is experimental and may change in a future release of Lima.
171+
# https://github.com/lima-vm/lima/pull/200
169172
# env:
170173
# KEY: value
171174

pkg/limayaml/limayaml.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ type LimaYAML struct {
2121
Probes []Probe `yaml:"probes,omitempty"`
2222
PortForwards []PortForward `yaml:"portForwards,omitempty"`
2323
Network Network `yaml:"network,omitempty"`
24-
Env map[string]*string `yaml:"env,omitempty"`
24+
Env map[string]*string `yaml:"env,omitempty"` // EXPERIMENAL, see default.yaml
2525
}
2626

2727
type Arch = string

0 commit comments

Comments
 (0)