Add support for more properties in launch.json's configurations objects

[smktpd]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

At the moment the extension supports quite a narrow set of options in a configuration object inside launch.json:
name, type, request, command, stackName, workDir, env, noDebug.
This limits the possible ways of usage of this extension quite a lot, by lacking 2 relatively important options:

1. envFile - I don't want to have important (including secret) values hardcode as envs in launch.json, I'd rather have a separate file (that may be stored somewhere outside project dir completely). Or I might have multiple configurations configured in launch.json (say, for preview and up) that should share the envs - Don't Repeat Yourself principle says it's better to not duplicate them, but rather point to the same place in both configurations. To do that- we need envFile added to the list of available properties of configuration objects.
2. args - currently the extension seems to be able to run only 2 combinations: pulumi preview and pulumi up and nothing else. How would I run pulumi up --skip-preview? How would I run pulumi preview --config-file /path/to/somewhere? Currently - your extension doesn't let me do any of that!

Affected area/feature

Debugging of Python-based Pulumi projects in VSCode.

[EronWright]

These are good ideas, and easily implemented IF the functionality is supported by the Pulumi automation API. To anyone interested, feel free to open PRs that add individual flags like skipPreview.

I suppose the extension could easily support envFile by reading the file (be sure to resolve the variables within the value). Similar to the nodejs launch config: https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_load-environment-variables-from-external-file