Is your feature request related to a problem? Please describe.
It's more complicated to manage the execution order of the scripts by renaming them, the scripts are managed by different teams and a change in 1 name would imply that all the other teams renamed their scripts
Describe the solution you'd like
Provide a .dat file for the task where the scripts that should be executed are listed 1 per line.
Example of dsc.dat file:
jobs\appjob.sql
jobs\serverjob.sql
app_permissions\appname.sql
app_permissions\appxpto.sql
This already exists in another extension and works well, also gives flexibility if we wan't to temporarily "disable" a script execution by removing that script from the .dat file instead of removing the script from source control.
Describe alternatives you've considered
Didn't considered other alternatives, because I worked like this in another extension and it worked well, just moved to this one because the other didn't provide a readable output when an error occured when executing scripts
Additional context
The extension I mention is SQL Toolkit parameter $executionOrder in this file
Component RunSqlCmdScripts
Is your feature request related to a problem? Please describe. It's more complicated to manage the execution order of the scripts by renaming them, the scripts are managed by different teams and a change in 1 name would imply that all the other teams renamed their scripts
Describe the solution you'd like Provide a .dat file for the task where the scripts that should be executed are listed 1 per line. Example of dsc.dat file: jobs\appjob.sql jobs\serverjob.sql app_permissions\appname.sql app_permissions\appxpto.sql
This already exists in another extension and works well, also gives flexibility if we wan't to temporarily "disable" a script execution by removing that script from the .dat file instead of removing the script from source control.
Describe alternatives you've considered Didn't considered other alternatives, because I worked like this in another extension and it worked well, just moved to this one because the other didn't provide a readable output when an error occured when executing scripts
Additional context The extension I mention is SQL Toolkit parameter $executionOrder in this file