Feature request: Allow for configuration to be stored in the settings file

[ntziolis]

We make heavy use of the .vscode/settings.json file to align settings across devs. Sadly this extension does not allow to store the configuration of which server should be installed and which files should be deployed. I understand that additional extensions are required, but lets assume those are already aligned across the team.

Sadly this means we cannot make use of this great extension since:

• the potential for misconfiguration is not small
• and we use devcontainers and configuration has to be re-done after each rebuild container
  • this happens very very often since we encourage our devs to rebuild every time they work on a new feature
  • which is to ensure that they have all the latest dependencies
  • the same also applies when using gitpod where the whole flow is based on re-creating a new dev environment from scratch every time you create a new workspace

Any chance configuration that can be checked into git is something you already have on the priority list?

[DerGernTod]

this would greatly simplify how teams work with this extension. our workflow includes starting a tomcat instance with multiple vm arguments (that point to project-specific paths) and deploying an exploded war on a special application context. the project contains multiple exploded war locations, depending on which app you want to load (they are all loaded into the same context). setting this up for each developer leaves a lot of potential for misconfiguration, as OP mentioned, that could be completely diminished with a simple settings.json file, or even launch.json options.

this can be compared to intellij run configs that allow multiple configs for each tomcat application context, and are simple xml files one can check into a vcs