argsFile and envFile in launch.json

Environment data

dotnet --info output:

.NET-Befehlszeilentools (2.0.2)
 
Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512
 
Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.2\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

VS Code version: 1.19.1 C# Extension version: 1.13.1

Feature request

In my launch.json I need to pass sensitive data (like passwords) as arguments (or environment variables). As the launch.json is also committed to Git it’s unwise to place the arguments in there. In NodeJS it is already possible to pass a file containing all the arguments (Microsoft/vscode#14523 and Microsoft/vscode-node-debug2@b3e2e8f3).

[gregg-miskelly]

Its closed because @SebastianPfliegel kindly submitted a PR to fix the part that he wanted. I don’t know off hand if VS Code makes the syntax you are suggesting there possible. But you are welcome to open another feature request issue.

[regul4rj0hn]

Sorry to necro but why is this closed? It is still not possible to use args in combination with the envFile. I guess that it would require a 2-step replacement on launch, which doesn’t seem to be implemented (or at least it is not working for me). Is that accurate?

E.g. support the following launch.json :

{
    "version": "0.2.0",
    "configurations": [
        {
          "name": "Launch",
          "type": "go",
          "request": "launch", 
          "mode": "debug",
          "host": "127.0.0.1",
          "program": "${workspaceFolder}/cmd/api",
          "envFile": "${workspaceFolder}/config/.env",
          "args": [
              "-smtp-username", "${env:SMTP_USERNAME}",
              "-smtp-password", "${env:SMTP_PASSWORD}",
              "-auth-url", "${env:AUTH_URL}",
              "-db-dsn", "${env:DB_DSN}",
          ],
          "showLog": true
        }
      ]
}

Expected Result: the args values that point to an env variable get replaced for the correct value whether they reside on the OS or the target envFile.