Ane 904 preflight check

[JeffreyHuynh1]

Overview

Broker currently has pretty good diagnostics through tracing and error messages, and we’re working on user-facing diagnostics through broker fix. However, all these diagnostics are confusing to users if they see something like “failed to upload scan” sometime after startup, instead of a more specific “Broker couldn’t reach FOSSA” at startup.

In order to catch obvious network misconfiguration early, we should add preflight checks to broker run. Most likely this is using the work implemented for broker fix, but with less output to the user unless there is an issue.

Acceptance criteria

When broker run is executed and after config values are parsed, Broker runs preflight checks.

These checks:

Validate that Broker can reach FOSSA using POST requests.

Validate that Broker can reach at least one integration.

Output detailed diagnostics for users explaining issues discovered during preflight checks.

Testing plan

• Manual test bad integration, broker fails
• Manual test bad fossa key, broker fails

Risks

• Added a guard to set FOSSA_API_KEY env variable for integration tests

References

• ANE-904

Checklist

• I added tests for this PR's change (or explained in the PR description why tests don't make sense).