docs: regenerate docs

Author: FabianKramm

docs/versioned_docs/version-5.18/commands/devspace_sync.md

@@ -44,8 +44,11 @@ devspace sync --container-path=/my-path
       --no-watch                   Synchronizes local and remote and then stops
       --pick                       Select a pod (default true)
       --pod string                 Pod to sync to
+      --polling bool               If polling should be used to detect file changes in the container
       --upload-only                If set DevSpace will only upload files
       --verbose                    Shows every file that is synced
+      --wait                       Wait for the pod(s) to start if they are not running
+
 ```
 
 
@@ -69,4 +72,3 @@ devspace sync --container-path=/my-path
       --var strings                  Variables to override during execution (e.g. --var=MYVAR=MYVALUE)
       --vars-secret string           The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars")
 ```
-

docs/versioned_docs/version-5.18/configuration/dependencies/git-repository.mdx

@@ -36,7 +36,7 @@ dependencies:
     ports: true
 dev:
   terminal:
-    imageName: api-server.server-image
+    imageSelector: ${runtime.dependencies.api-server.images.server-image}
 ```
 
 :::info Authentication

docs/versioned_docs/version-5.18/configuration/variables/runtime-variables.mdx

@@ -73,7 +73,7 @@ dev:
   # Will open a terminal to the pod with the 
   # image from dep1
   terminal:
-    imageName: ${runtime.dependencies.dep1.images.image1}
+    imageSelector: ${runtime.dependencies.dep1.images.image1}
 ```
 
 </TabItem>
@@ -124,5 +124,5 @@ dev:
   # Will open a terminal to the pod with the 
   # image from dep1
   terminal:
-    imageName: ${runtime.dependencies.dep1.images.image1}
+    imageSelector: ${runtime.dependencies.dep1.images.image1}
 ```

docs/versioned_docs/version-5.18/configuration/variables/source-command.mdx

@@ -88,4 +88,26 @@ vars:
 
 ### `default`
 
-If the command returns nothing, this is the value that will be used for this variable.
+If the command returns nothing, this is the value that will be used for this variable.
+
+### `alwaysResolve`
+
+If enabled, the variable will be loaded even though it is not used within the config. This might be useful for variables that should be resolved after a config expression is applied. E.g.:
+
+`devspace.yaml`:
+```
+vars:
+- name: my-var
+  value: my-value
+  alwaysResolve: true
+hooks:
+- name: my-hook
+  command: $(cat command.txt)
+  events: ["after:deploy"]
+```
+
+`command.txt`:
+```
+echo Hello ${my-var}!
+```
+

docs/versioned_docs/version-5.18/configuration/variables/source-env.mdx

@@ -34,3 +34,24 @@ If `source` is `env` and the environment variable is **not** defined, DevSpace w
 ### `default`
 
 <FragmentVarsDefault/>
+
+### `alwaysResolve`
+
+If enabled, the variable will be loaded even though it is not used within the config. This might be useful for variables that should be resolved after a config expression is applied. E.g.:
+
+`devspace.yaml`:
+```
+vars:
+- name: my-var
+  value: my-value
+  alwaysResolve: true
+hooks:
+- name: my-hook
+  command: $(cat command.txt)
+  events: ["after:deploy"]
+```
+
+`command.txt`:
+```
+echo Hello ${my-var}!
+```

docs/versioned_docs/version-5.18/configuration/variables/source-input.mdx

@@ -177,3 +177,24 @@ If the provided value does **<u>not</u>** match the regex in `validationPattern`
 
 ### `validationMessage`
 The `validationMessage` option expects a string stating an error message that is shown to the user when providing a value for the variable that does not match the regex provided in [`validationPattern`](#validationpattern).
+
+### `alwaysResolve`
+
+If enabled, the variable will be loaded even though it is not used within the config. This might be useful for variables that should be resolved after a config expression is applied. E.g.:
+
+`devspace.yaml`:
+```
+vars:
+- name: my-var
+  value: my-value
+  alwaysResolve: true
+hooks:
+- name: my-hook
+  command: $(cat command.txt)
+  events: ["after:deploy"]
+```
+
+`command.txt`:
+```
+echo Hello ${my-var}!
+```

docs/versioned_docs/version-5.18/configuration/variables/source-none.mdx

@@ -41,3 +41,24 @@ The `value` option expects a string, integer or boolean defining the value for t
 
 - The used variable is defined before the variable that wants to use it
 - The used variable is a predefined variable
+
+### `alwaysResolve`
+
+If enabled, the variable will be loaded even though it is not used within the config. This might be useful for variables that should be resolved after a config expression is applied. E.g.:
+
+`devspace.yaml`:
+```
+vars:
+- name: my-var
+  value: my-value
+  alwaysResolve: true
+hooks:
+- name: my-hook
+  command: $(cat command.txt)
+  events: ["after:deploy"]
+```
+
+`command.txt`:
+```
+echo Hello ${my-var}!
+```

docs/versioned_docs/version-5.18/fragments/config-vars.mdx

@@ -2,6 +2,7 @@
 vars:                               # struct[]  | Array of config variables
 - name: CONFIG_VAR                  # string    | Name of the config variable
   value: my-value                   # any       | The fixed value of the config variable
+  alwaysResolve: false              # bool      | If enabled, the variable will be loaded even though it is not used in config
   question: "What is CONFIG_VAR?"   # string    | Question to ask the user if no value is found for variable
   options: []                       # string[]  | Options for picker (selector) to show to user (to choose a value for variable)
   noCache: false                    # bool      | Disable caching and prompt for value on every run.