Variable override in command not working

[markphillips100]

What happened?
Upgraded from v6.0.0-alpha.7 to v6.0.0-alpha.16 and variable override in run command no longer applied.

What did you expect to happen instead?
Specified variable should be used in called command.

How can we reproduce the bug? (as minimally and precisely as possible)

1. Install v6.0.0-alpha.7
2. Run devspace run cmd1
   Output should be "some value".
3. Run devspace run cmd2
   Output should be "A different value".
4. Install v6.0.0-alpha.16
5. Run devspace run cmd1
   Output should be "some value".
6. Run devspace run cmd2
   Output should be "A different value" but is still "some value".

My devspace.yaml:

version: v2beta1
name: devspacetest

vars:
  VAR1:
    value: "some value"

commands:
  cmd1: |-
    echo ${VAR1}
  cmd2: |-
    devspace --var VAR1="A different value" run cmd1

Local Environment:

• DevSpace Version: v6.0.0-alpha.7 & v6.0.0-alpha.16
• Operating System: windows

Anything else we need to know?
Is this an expected change and if so how should we apply variable overrides to run commands moving forward?

/kind bug

[FabianKramm]

@markphillips100 thanks a lot for creating this issue! I created a PR for this that should fix the problem. Meanwhile you can use the following workaround:

version: v2beta1
name: devspacetest

vars:
  VAR1: $(echo ${VAR1:-"some value"})

commands:
  cmd1: |-
    echo ${VAR1}
  cmd2: |-
    VAR1="A different value" devspace run cmd1

[markphillips100]

Thanks @FabianKramm. Will the PR be merged into the next alpha release do you think?

[FabianKramm]

@markphillips100 yes it will be!