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
Copy file name to clipboardExpand all lines: docs/pages/configuration/expressions.mdx
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,6 +129,17 @@ Expressions are run in a golang shell that is syntax compatible to a regular POS
129
129
Variables are resolved before and after applying expressions, which means that you can load a section from file within an expression that contains a variable which will still be resolved afterwards.
130
130
:::
131
131
132
+
:::warning Unsupported Config Expressions
133
+
Expressions are not supported in these configuration properties:
134
+
- `vars`
135
+
- `profiles[*].name`
136
+
- `profiles[*].parent`
137
+
- `profiles[*].parents`
138
+
- `profiles[*].activations`
139
+
- `profiles[*].patches[*].op`
140
+
- `profiles[*].patches[*].path`
141
+
:::
142
+
132
143
### Testing Config Expressions
133
144
134
145
The command `devspace print` can be used to test your config expressions and shows the config after all profiles, variables and expressions were applied.
0 commit comments