docs: add variables via cli box

Author: FabianKramm

docs/pages/configuration/variables/basics.mdx

@@ -98,15 +98,20 @@ The `source` option of a config variable expects either:
 - [`input`](../../configuration/variables/source-input.mdx) means to ask the user a question **once** (values will be cached in `.devspace/generated.yaml`)
 :::
 
+:::warning Pass Variables via CLI
+A useful feature in DevSpace is that you can also specify variables as flags, which will override previous values (if there are any):
+```
+devspace deploy --var VAR1=VALUE1 --var VAR2=VALUE2
+```
+:::
+
 :::note Input Caching
 If `source` is either `all` or `input` and the variable is not defined, the user will be asked to provide a value either using a generic question or the one provided via the [`question` option](../../configuration/variables/source-input.mdx#question). The user-provided value will be cached in `.devspace/generated.yaml` and the user will only be asked again after the cache has been cleared first using:
 ```bash
 devspace reset vars
 ```
 :::
 
-
-
 ## Predefined Variables
 DevSpace provides some variables that are filled automatically and can be used within the config. These can be helpful for image tagging and other use cases:
 

pkg/devspace/dependency/dependency_test.go

@@ -1,6 +1,7 @@
 package dependency
 
 import (
+	"github.com/devspace-cloud/devspace/pkg/devspace/hook"
 	"io/ioutil"
 	"os"
 	"path/filepath"
@@ -333,6 +334,9 @@ func TestDeployAll(t *testing.T) {
 			resolver: &fakeResolver{
 				resolvedDependencies: testCase.resolvedDependencies,
 			},
+			hookExecuter: hook.NewExecuter(&latest.Config{
+				Dependencies: testCase.dependencyTasks,
+			}),
 		}
 
 		err = manager.DeployAll(testCase.options)
@@ -579,6 +583,7 @@ type deployTestCase struct {
 	forceDependencies bool
 	skipBuild         bool
 	forceBuild        bool
+	skipDeploy        bool
 	forceDeploy       bool
 
 	expectedErr string
@@ -672,7 +677,7 @@ func TestDeploy(t *testing.T) {
 		}).Resolve(false)
 		dependency := dependencies[0]
 
-		err = dependency.Deploy(testCase.skipPush, testCase.forceDependencies, testCase.skipBuild, testCase.forceBuild, testCase.forceDeploy, log.Discard)
+		err = dependency.Deploy(testCase.skipPush, testCase.forceDependencies, testCase.skipBuild, testCase.forceBuild, testCase.skipDeploy, testCase.forceDeploy, log.Discard)
 
 		if testCase.expectedErr == "" {
 			assert.NilError(t, err, "Error purging all in testCase %s", testCase.name)