-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for different configs per environment #10
Comments
Hey @jasonchester! I could make We also need For example, we have:
and
Then when you use it in your code: Another option would be to store everything in For example:
Is this something similar to what you had in mind? |
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.
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. |
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 So dynamically loaded tasks with oradew task provider could not be executed as commands as it is done now but only as tasks. |
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... |
Would like to pass different template variables per environment in to the scripts.
My use case is for a custom SEND_MAIL package.
v_email_server VARCHAR2(30) := '${config["version.number"]}';
The text was updated successfully, but these errors were encountered: