| Age | Commit message (Collapse) | Author |
|
Force-Push: initial development
Change-Id: I2966407941866c422a0702776cadeb2b8263621e
|
|
this produces a list of secrets, although it doesn't yet do any of the checking to see if the files actually exist, when they were modified, etc. it just prints the parsed data structure.
this was kind of a pain to test, I had to make a fake machine config with some secrets and point it to it. we should figure out a way to use Rust's test framework to do that automatically, but that can be in a future CL, and I don't necessarily have to be the one to write it.
Change-Id: I4c7d579d61e8f3694fe879998dae0f95baaeea05
|
|
Change-Id: I5e1570940fedf52bb560fd824270e201757004ed
|
|
Change-Id: Ifec5dbbe20b2c625d448eba436620622af6c5120
|
|
hopefully this will make the diffs more readable; otherwise the entire
JSON file is a single huge line...
depending on Perl feels heavyweight but keep in mind that Perl is already a
mandatory part of any Linux system I'm familiar with, and it has a very
nice JSON pretty-printer
Change-Id: I817b4f6b63152673b31aeb32a3255d4c1b83942e
|
|
I've never done this before and am really proud of the code; I hope the
comments help but feel free to ask questions.
As you can see by looking at the diffs to `options.nix`, it did catch
several issues that had gotten through up to this point. I'm pretty
pleased with that. As before, `nix flake check` is all you need to do to
run it.
Change-Id: I99a550e92d7b4770e52b6aba763cff2bdc4c9287
|
|
this also adds the beginnings of a test harness; the test harness will
become useful in a future CL, but for now `nix flake check` should
continue to do what we want it to, and maybe slightly more
Change-Id: I7f05bcb5588f2b52d79cf05cf22263f084e8be49
|
|
Change-Id: I314d0350b03fedebeedc7eddedf409a286719486
|
|
I also took the liberty of adding some Rust libraries that I know will
be useful
Change-Id: Id5d98d86cdce653f6706903b75e285c72f2ba4b4
|
|
|