VSCode Dump

In followup of issue Azure/logicapps#664 we currently face an issue with the log analytics managed api connection (and likely other managed api connections) in VS code.

Each time we save the workflows, the connections.json, local.settings.json and parameters.json gets edited in a way which is not desirable, because we have parameterized it ourselves.

Result is that the connections and parameters.json is deployed to Azure with data which is not present and a bearer token which is valid for 7 days (

Steps to Reproduce the Bug or Issue

1. Please note how the connections.json looks before save:

2. Please note how the parameters.json looks before save:

3. Please note how the local.settings.json looks before save:

4. As can be seen, we have parameterized the api connection both for vscode (and during deployment) for setting up the api connection.

5. Edit a workflow.json and save it

6. You will see that the 3 files are aedjusted by VS code

7. The connections.json managed api section is overridden as follows:

8. The parameters.json is also adjusted to contain the runtime url and an authentication section for a temp vscode bearer token which is valid for 7 days.

9. The local.settings.json contains the bottom 2 entries after save, which is the runtime url and the token itsel

Result is, that this gets deployed and because the connection.json references incorrect appsettings (like WORKFLOWS_SUBSCRIPTION_ID, WORKFLOWS_LOCATIONS_NAME and the raw bearer token. And therefore the logic app workflows do not work.

What I would expect: A save should not trigger these changes to files that are being deployed.