Disable console logs for every changeset

Environment

Liquibase Version: 4.7.1

Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>

Liquibase Extension(s) & Version:

Database Vendor & Version:

Operating System Type & Version:

Description

Since 4.7.1 every changeset is logged to SOUT, and it seems like there is no way to turn it off. For us that means that tests logs are complete unusable during to hight amount of tests & changesets.

Steps To Reproduce

Just run the migration.

Actual Behavior

For every change set a message in system out is appeared:

Running Changeset: db/changelog/db.changelog-file.xml::version::author

Expected/Desired Behavior

No message in SOUT. A way to completely replace ConsoleUIService with LoggerUIService so every message could be controlled by logger implementation

[bmarwell]

Here’s the reason it appeared:

https://github.com/liquibase/liquibase/commit/26f9eac8d4958455c06c2c6e97c12c19c1666dfd

Those lines are “new”: https://github.com/liquibase/liquibase/commit/26f9eac8d4958455c06c2c6e97c12c19c1666dfd#diff-e48270cbddf72e544cefef4081d2066ece7c1955b433fe7301308b75315c8d1bR46-R49

Before this change, no output was on stdout. Now I have it twice: In my custom logging implementation (liquibase-slf4j) AND on stdout. This happens to all my junit tests.

Can you please re-evaluate this commit?

// Edit:

Workaround for Library users is to use the code directly just before the update instruction:

   try {
        Scope.enter(Map.of(Scope.Attr.ui.name(), new LoggerUIService()));
      } catch (Exception e) {
        log.error("", e);
      }

// Edit 2:

For large projects, the build output (eg Maven builds) get considerably more output. A few hundred lines per test or test class is not something unheard of. The added output can greatly impact build times. It appears out of nowhere after updating the dependency (liquibase). The workaround is surprising at best and needs to be inserted before every update statement.

[jeenkhoorn]

Any updates on a fix for this issue?