You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
![image](https://private-user-images.githubusercontent.com/36156950/246454556-16b47c0d-2576-410b-a37e-bbd74bd23d35.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MTI5NzQsIm5iZiI6MTczODkxMjY3NCwicGF0aCI6Ii8zNjE1Njk1MC8yNDY0NTQ1NTYtMTZiNDdjMGQtMjU3Ni00MTBiLWEzN2UtYmJkNzRiZDIzZDM1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDA3MTc1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNiM2E0NTQ0YjVlNWE4YjQwZDBjMzIyMGVkMmE2MmIyYWVlZDZmOGRmZmNlOTBhNWYxODE3MTE5NDE4YjJjODYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.4SdC7Pjy-t-pYN1P_HEALK_lMsfwTrCnqJe567ALwLI)
The extension I mention is SQL Toolkit parameter $executionOrder in this file
The text was updated successfully, but these errors were encountered: