-
Notifications
You must be signed in to change notification settings - Fork 247
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
Shell scripts #384
Comments
Thank you for your suggestion. Do you have any examples of concrete use-cases where you want shell scripts to be run in a special order together with your sql scripts? |
|
I think this would be a great feature. |
I'm not totally sure these kinds of script should be inside the RoundhousE world, though. Why would you need the RH semantics for such scripts? Couldn't this be another part of the release? I'm open to being convinced otherwise, by all means, but it is dependent on someone taking ownership of this feature, as my time is very limited, I'm afraid. Do you have any suggestions as to how the feature should work? Should there be "drivers" for each external script type (e.g. PowerShell, bash, cmd, python, etc), should they all be dependent on the enviroment? Which context should they run in? |
I would make this as simple as possible. PowerShell only (via it you can do all things you mention) with exactly the same triggers as with sql and yet are done only in context of migrations.
I already provided the reasons in the comment above. Many things are not possible with sql only.
Sure, in FOSS world this is absolutely normal. |
You should support running shell scripts as a part of migration for more complex scenarios.
The text was updated successfully, but these errors were encountered: