Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / refs/heads/master
commitc3fb066bcea5e8a39d85c3a9754cf3d666a68d83[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Tue Sep 23 17:42:30 2025 -0400
committerPatrick Williams <patrick@stwcx.xyz>Tue Sep 23 17:46:47 2025 -0400
tree84f5bc05d137f945eddad4c1b0b6edb7796c22ba
parent210514d3061b9256213112b5e072a3a3cd835c1b [diff]
tof-votes: acceptable: load from YAML

Set the regex pattern file to be loaded from YAML rather than
embedded in Python.  This allows it to be referenced from
elsewhere, if needed, such as by the openbmc-bot[1].

[1]: https://lore.kernel.org/openbmc/aM9suaMKrCk9PY-T@heinlein/

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1941e3bb48227e8171575326603dd440fe722d22
2 files changed
tree: 84f5bc05d137f945eddad4c1b0b6edb7796c22ba
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bbdbg/
  5. bi2cp/
  6. check_journal/
  7. cla-signers/
  8. dbus-pcap/
  9. dbus-vis/
  10. dbus_sensor_tester/
  11. dbusView/
  12. ddconvnotrunc/
  13. expectedJsonChecker/
  14. format-yaml/
  15. i2c/
  16. ipkdbg/
  17. netboot/
  18. openbmc-autobump/
  19. openbmctool/
  20. overlay/
  21. pldm/
  22. prepare-emmc-qemu/
  23. pretty-journal/
  24. pwmtachtool/
  25. reboot/
  26. reboot-ping-pong/
  27. rootfs_size/
  28. sensor_yaml_config/
  29. tof-voters/
  30. tracing/
  31. witherspoon-debug/
  32. .linter-ignore
  33. .shellcheck-ignore
  34. LICENSE
  35. OWNERS
  36. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.