Log filename when executing migration #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding the full filename being executed during the migration.
Perhaps this is specific to our use case but we usually name our migration files based on release number and business area of the application that it applies to. Something like 20192205100500-service1-1.2.0.
We then use a different timestamp with the same migration name if we need another migration in that same release.
The timestamp therefore allows us to identify the release script we are executing precisely which is why logging the filename is useful we find.