Support for quiet operations about goose HOT 4 CLOSED

Absolutely. I thought that was the case already. If you use the library, you can set a disabled logger, or if using the CLI if you don't supply the verbose flag, it doesn't print anything.

If that's not the case, I could see us introducing –-quiet flag or equivalent.

from goose.

To clarify, I am using the library because some of my migrations are Go-flavored. I'm not sure I understand how to disable logging that is buried like in these two examples:

• goose/migration.go

  Line 235 in 76946cc

  log.Printf("OK %s (%s)\n", filepath.Base(m.Source), finish)

• goose/up.go

  Line 127 in 76946cc

  log.Printf("goose: successfully migrated database to version: %d\n", current)

Based on how the logger is initialized in

Thank you

from goose.

All of the log identifiers are for the "custom" logger and not the standard lib one.

In #383 we added a noop logger, so something like this might work:

goose.SetLogger(goose.NopLogger())

Or, if you use goose.NewProvider and call methods, they should all be "quiet" by default unless you enable verbose.

from goose.

Thank you, the approach with

goose.SetLogger(goose.NopLogger())

helped. I am closing the issue.

from goose.