-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to msgpack #3728
Migrate to msgpack #3728
Conversation
Also remember migration states to not run migrations over and over again.
m.log.Info().Msg("Skipping finished migration " + migration + "...") | ||
continue | ||
case "": | ||
m.log.Info().Msg("Running migration " + migration + "...") | ||
default: | ||
m.log.Info().Msg("Re-running migration " + migration + "...") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably drop any logs that show up during startup unless a migration actually needs to happen. We can think of passing down a logger or better just context the whole chain of services to clean this up in a subsequent PR.
But for now lets silence these logs, ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll push an according commit soon.
No description provided.