[recipe_wrapper] Actually invoke attestation_tool

This change adds actually invoking the attestation_tool. The test runs using
the `attestation_tool` when it can, or drops back to the fake when it can't.
Because the output of the tool is non-deterministic at runtime due to the fact
the tool appears to use clock time as a seed, what's tested is the output can
be parsed and look for the values known not to change.

As the attestation_tool on success doesn't actually return any output, the test
was able to be simplified.

I don't love how the I/O here is limited to communicating with files that are
written/read/cleaned up, but I don't think there's anything smarter to be done
here, just isolate the tool as best as possible to allow for idomatic data
passing internally.

The current input to the tool is fake and needs to actually be formulated to
something reasonable with CIPD and such, but that's for later.

Bug: b/297416582
Change-Id: Ied9fcfc8c36ee0bc525216e94397664e938d323c
Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/infra/+/909334
Reviewed-by: Anthony Fandrianto <atyfto@google.com>
Commit-Queue: Chris Lewis <cflewis@google.com>
3 files changed
tree: ba65efa6d4a7e1b95872de4296d707fc08519817
  1. artifacts/
  2. buildbucket/
  3. checkout/
  4. cmd/
  5. execution/
  6. flagutil/
  7. functools/
  8. gerrit/
  9. gitiles/
  10. monorail/
  11. rpcutil/
  12. scripts/
  13. third_party/
  14. vendor/
  15. .gitignore
  16. AUTHORS
  17. go.mod
  18. go.sum
  19. LICENSE
  20. manifest
  21. PATENTS
  22. README.md
README.md

infra

This repo contains tools and config files necessary to run infrastructure related to builds, code review, version control, and continuous integrations.