Add -o --output parameters to DB seeder util for preset command#7495
Add -o --output parameters to DB seeder util for preset command#7495theMickster merged 6 commits intomainfrom
Conversation
… readable output when piping into other tooling
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed the addition of Code Review DetailsNo blocking findings. The change is small, self-contained, and limited to a dev utility. Validation and parsing are consistent ( |
|
New Issues (2)Checkmarx found the following issues in this Pull Request
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7495 +/- ##
=======================================
Coverage 59.13% 59.13%
=======================================
Files 2077 2077
Lines 91848 91848
Branches 8175 8175
=======================================
+ Hits 54315 54316 +1
+ Misses 35601 35600 -1
Partials 1932 1932 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
theMickster
left a comment
There was a problem hiding this comment.
Couple things to change and one point of discussion to clarify
Co-authored-by: Mick Letofsky <mletofsky@bitwarden.com>
|





🎟️ Tracking
📔 Objective
When working with some automation and the DB seeder utility around the
presetcommand, I found it was hard to get machine-readable output in the existing format while using the preset command. This adds a new parameter for output, used with-o,--outputwith a new argsjson,text(default).Using
if (!Console.IsOutputRedirected)in conjunction with a JSON output lets us pipe directly into tools likejqto grab what we need.For example:
📸 Screenshots