Add liquibase TOML filter#1036
Conversation
📊 Automated PR Analysis
SummaryAdds a new built-in liquibase TOML filter that strips banners, ASCII art, and verbose info logs from liquibase CLI output. Introduces a Review Checklist
Analyzed automatically by wshm · This is an automated analysis, not a human review. |
901a98a to
630f0a2
Compare
pszymkowiak
left a comment
There was a problem hiding this comment.
Rebased on develop to clear the Cargo.toml / Cargo.lock / CHANGELOG / manifest noise — PR is now clean (1 commit, 5 files, feature-only).
Tested locally with a mock liquibase binary emitting banner on stderr:
| Test | Result |
|---|---|
rtk verify --filter liquibase |
4/4 passed |
| Real execution (raw → filtered) | 705 bytes → 133 bytes (90% savings) |
| Empty output | liquibase: ok |
| Error with exit 1 | Error visible, exit code propagated |
The filter_stderr field is a solid addition — it's a generic feature that will help other JVM tools (Maven, Gradle, Ant) that emit banners to stderr. Default is false, so no impact on existing filters.
LGTM — good to merge.
Removes ASCII art header and Java startup boilerplate from Liquibase output while preserving changeset execution list and migration result. Saves 80%+ tokens on typical update output. Filter strips: - ASCII art logo (lines starting with ##) - Verbose startup lines (Starting Liquibase at, Liquibase Version) - Empty lines Preserves: - Running Changeset lines (migration execution) - Rolling Back Changeset lines (rollback operations) - Success/failure result lines - ERROR messages Includes 3 inline tests covering update success, error handling, and rollback scenarios. Upstream: v0.36.0 rtk-ai#1036
Summary
Verification