Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / refs/heads/factory-rex-15708.B
commit55ec79ce4afc543a9e50b18a9a1f4fd00b81353d[log] [tgz]
authorSarthak Kukreti <sarthakkukreti@google.com>Tue Sep 12 23:33:24 2023
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Sep 19 18:14:13 2023
tree7eeb6f1068bd75e9a9a5269354df667792b986ea
parent652894ea880dfd0ed451f1bc16e4e428722c281b [diff]
redaction_tool: Add LVM UUIDs

vgcfgbackup can contain non-standard LVM UUIDs

Note that this doesn't uprev the entire redaction_tool util since
it has a dependency on an re2 uprev

BUG=b:232006113
TEST=CQ

Change-Id: I252b4b367d07fe9ce8b6e48a126327f47ec2262f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/4875297
Tested-by: Sarthak Kukreti <sarthakkukreti@google.com>
Reviewed-by: Donna Dionne <donnadionne@google.com>
Reviewed-by: Miriam Zimmerman <mutexlox@chromium.org>
Tested-by: Donna Dionne <donnadionne@google.com>
Commit-Queue: Sarthak Kukreti <sarthakkukreti@google.com>
2 files changed
tree: 7eeb6f1068bd75e9a9a5269354df667792b986ea
  1. BUILD.gn
  2. DIR_METADATA
  3. ip_address.cc
  4. ip_address.h
  5. libmetrics_metrics_recorder.cc
  6. libmetrics_metrics_recorder.h
  7. libmetrics_metrics_tester.cc
  8. libmetrics_metrics_tester.h
  9. metrics_tester.h
  10. OWNERS
  11. pii_types.h
  12. PRESUBMIT.cfg
  13. README.md
  14. redaction_tool.cc
  15. redaction_tool.h
  16. redaction_tool_metrics_recorder.h
  17. redaction_tool_unittest.cc
  18. url_canon.h
  19. url_canon_internal.cc
  20. url_canon_internal.h
  21. url_canon_ip.cc
  22. url_canon_ip.h
  23. url_canon_stdstring.cc
  24. url_canon_stdstring.h
  25. url_parse.h
  26. validation.cc
  27. validation.h
README.md

redaction_tool: PII Redaction Tool

A redaction_tool redacts PII using a wide set of RegEx expressions.

This code is a mirror of https://source.chromium.org/chromium/chromium/src/+/main:components/feedback/redaction_tool/

Changes should be made in chromium code base only and then be upreved here.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update
  • git checkout -b main cros/main
  • git merge cros/upstream/main
    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.
  • Push the resulting merge commit for review with:
    • git push HEAD:refs/for/main