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
Currently, the migrations collection only keeps track of the current migration and whether or not control is locked. While this is helpful information, it'd be great if there was an option for the package to insert a document in the collection that stored what migration ran, when it ran, if it was successful, and which direction it was run. It may be something that is disabled by default and enabled with a configuration option.
The text was updated successfully, but these errors were encountered:
I also just thought of something to go along with this: if logging is enabled and a migration fails, since that's being logged, it'd be helpful to log the error message if possible as well. I just ran into an issue where at some point after deploying with mup, migrations locked and I'm having trouble finding it in the mup logs.
Currently, the migrations collection only keeps track of the current migration and whether or not control is locked. While this is helpful information, it'd be great if there was an option for the package to insert a document in the collection that stored what migration ran, when it ran, if it was successful, and which direction it was run. It may be something that is disabled by default and enabled with a configuration option.
The text was updated successfully, but these errors were encountered: