"compounds": [
{
"name": "Multi-launch DataService & Controlplane with Bertie",
"configurations": [
"Launch DataService with Bertie",
"Launch Controlplane with Bertie"
]
},
When I would launch "Multi-launch DataService & Controlplane with Bertie" it would launch two versions of whichever folder was defined first. If ControlPlane is defined first, it does two ControlPlane instances. If DataService is defined first, it does two DataService instances.
To Reproduce
Steps to follow to reproduce this issue.
**Expected behavior**
Bridge to Kubernetes should still launch both projects listed in the folder -- not two instances of the first folder it finds.
**Logs**
Attach logs from the following directory:
For Windows: %TEMP%/Bridge to Kubernetes
For OSX/Linux: $TMPDIR/Bridge to Kubernetes
If you are a Visual Studio user,
- Set the environment variable MS_VS_AZUREDEVSPACES_TOOLS_LOGGING_ENABLED=true
- Open Visual Studio and run your scenario
- Provide logs from: %temp%\Microsoft.VisualStudio.Kubernetes.Debugging
**Environment Details**
Client used (VS Code/Visual Studio):
Client's version:
Operating System:
**Additional context**
Add any other outputs from the clients or context you would like to share.
Describe the bug My workspace defines two folders:
{ "path": "../src/Services/ControlPlane/ControlPlane" }, { "name": "DataService", "path": "../src/Services/DataService/Server" },
and a compound
"compounds": [ { "name": "Multi-launch DataService & Controlplane with Bertie", "configurations": [ "Launch DataService with Bertie", "Launch Controlplane with Bertie"
When I would launch "Multi-launch DataService & Controlplane with Bertie" it would launch two versions of whichever folder was defined first. If ControlPlane is defined first, it does two ControlPlane instances. If DataService is defined first, it does two DataService instances.
I downgraded VS Code from
Version: 1.65.0 (user setup) Commit: b5205cc8eb4fbaa726835538cd82372cc0222d43 Date: 2022-03-02T11:12:08.962Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19044
back to
Version: 1.64.2 (user setup) Commit: f80445acd5a3dadef24aa209168452a3d97cc326 Date: 2022-02-09T22:02:28.252Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19044
and the issue went away.
To Reproduce Steps to follow to reproduce this issue.
**Expected behavior** Bridge to Kubernetes should still launch both projects listed in the folder -- not two instances of the first folder it finds. **Logs** Attach logs from the following directory: For Windows: %TEMP%/Bridge to Kubernetes For OSX/Linux: $TMPDIR/Bridge to Kubernetes If you are a Visual Studio user, - Set the environment variable MS_VS_AZUREDEVSPACES_TOOLS_LOGGING_ENABLED=true - Open Visual Studio and run your scenario - Provide logs from: %temp%\Microsoft.VisualStudio.Kubernetes.Debugging **Environment Details** Client used (VS Code/Visual Studio): Client's version: Operating System: **Additional context** Add any other outputs from the clients or context you would like to share.