Support for different configs per environment about oradew-vscode HOT 4 CLOSED

Hey @jasonchester!

I could make oradewrc.json be the base configuration and then optional overload configurations for environments (oradewrc.test.json, oradewrc.uat.json).

We also need TEST: Package and UAT: Package command for running environemnt specific packaging command.

For example, we have:
oradewrc.json:

{
...
...
  "customField": "this is it."
}

and
oradewrc.test.json:

{
  "customField": "..no this."
}

Then when you use it in your code: '${config["customField"]}' and package it with TEST: Package command, it would replace it with "..no this." instead of "this is it.".

Another option would be to store everything in oradewrc.json and have env-prefixed variables.

For example:
oradewrc.json:

{
...
...
  "customField": "this is it.",
  "TEST:customField": "..no this."
}

Is this something similar to what you had in mind?

from oradew-vscode.

Yes, this would be perfect. I like the file per environment approach as opposed to the prefixed variables because it is easier to work with.

• Easier a source control versioning
• Easier to compare environment settings with diff tooling
• Similiar to how other systems have implemented env configs ie. dotnet core

As far as the new environment based packaging commands, i am wondering if it would be better if oradew implemented a Task Provider which could parse the dbconfig.json and generate task definitions for each one defined.

Thanks again.

from oradew-vscode.

I was thinking about Task provider approach just recently...

One disadvantage would be that you can not dynamically bind extension commands to Command palette or UI, as far as I know, but you have to add them manually to extension's package.json file.

So dynamically loaded tasks with oradew task provider could not be executed as commands as it is done now but only as tasks.

from oradew-vscode.

Environment-specific file configs are now available. @jasonchester, you can try them out.

About implementing task provider for oradew commands, I suggest opening maybe a new issue for the request...

from oradew-vscode.