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
In some scenarios, where you want to push the configuration file into source control, these scenarios include:
Repeatable migration
Sharing with the team
Versioning the last migration
In these scenarios the developer has to manually write and delete the connection string for the source and sink to avoid pushing them into source control. Obviously, mistakes happen and the connection string is pushed into source control.
Could you provide a solution to solve this problem? One suggestion is overriding the connection string via command line arguments, so the connection string in a migration file can be empty.
The text was updated successfully, but these errors were encountered:
In some scenarios, where you want to push the configuration file into source control, these scenarios include:
In these scenarios the developer has to manually write and delete the connection string for the source and sink to avoid pushing them into source control. Obviously, mistakes happen and the connection string is pushed into source control.
Could you provide a solution to solve this problem? One suggestion is overriding the connection string via command line arguments, so the connection string in a migration file can be empty.
The text was updated successfully, but these errors were encountered: