Make it possible to specify path for command execution in its configuration

[mshaposhnik]

Description

To make command execution more flexible and compatible with new devfile feature, it is proposed to add possibility to specify the path inside machine where the command should be executed.
It can be passed through the workingDir attribute of the command.
Example:

{ 
 "commandLine": "mvn clean install", 
  "name": "console-java-simple:build", 
  "attributes": { 
        "goal": "Build", 
        "machineName": "dev-machine", 
  >>>>>>"workingDir": "/projects/console-java-simple"
    }
}

[garagatyi]

In Che 7 use-case machine name is controlled by a plugin author and Che master code. So, it is subject to change without user awareness. And if this happens a command would not work.

[AndrienkoAleksandr]

Blocked kubernetes/kubernetes#71350 (comment)

[AndrienkoAleksandr]

Blocked by kubernetes/kubernetes#71350

[l0rd]

Can't we just cd <working-dir>; <command>?

[l0rd]

@AndrienkoAleksandr ^^ ?

[AndrienkoAleksandr]

Can't we just cd <working-dir>; <command>?

Yes, we can do it like workaround.

[l0rd]

Yes, we can do it like workaround.

Ok let's start with that because I am afraid it will take years to have a patch on Kubernetes

[sleshchenko]

@AndrienkoAleksandr Looks like exec sidecar respects workingDir in command attributes, does not matter with a workaround (cd workindDir && ...), right?
If yes, then can we close this issue?

[skabashnyuk]

@AndrienkoAleksandr wdyt ??