Support for quiet operations

[servernoj]

I run goose (for migrate up) as part of the dockertest setup, where a new container gets created and purged for every integration test.

I have about 10 migrations (so far), so I see the entire list printed for every test to acknowledge successful migration.

Would it be possible to introduce an option to enable quiet operations for situations like mine?

Thank you.

[mfridman]

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.

[servernoj]

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

goose/log.go

Line 7 in 76946cc

var log Logger = &stdLogger{}

I don't see a way to disable it via options passed to Run() method

Thank you

[mfridman]

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.

[servernoj]

Thank you, the approach with

goose.SetLogger(goose.NopLogger())

helped. I am closing the issue.