Ane 1252 preflight check

[JeffreyHuynh1]

Overview

As a fossa user, I want fossa to perform pre-flight mode so I’m confident that my API key, and configuration and dependency files are valid.

Acceptance criteria

• If fossa-cli, has invalid API key for action, it should halt prior to analysis or any actions that requires API key

• If fossa-cli, has invalid fossa-deps, it should halt prior to analysis or any actions

• If fossa-cli, has invalid fossa-yml, it should halt prior to analysis or any action

• If fossa-cli, should be able to connect to access app.fossa.com for any command that requires VALID API Key (or halt)

If fossa-cli, should be able to write to temp directory in the system

Testing plan

PreflightChecksSpec:

• mock failed and successful calls to getOrganization

Manually tested related commands with invalid api key

Risks

Metrics

References

• ANE-1252

Checklist

• [x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• [x] If this PR introduced a user-visible change, I added documentation into docs/.
• [x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• [x] If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
• [x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• [x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

[JeffreyHuynh1]

The ticket specified to validate the .fossa.yml and fossa-deps.yml configs.

.fossa config is validated at parsing and an error will be thrown if the config isn't correct. Fossa-deps is only used in fossa analyze so I just moved that function call to validate fossa-deps earlier on in the analyze work flow. As a result, I didn't include the validation for .fossa and fossa-deps it in the preflightChecks function to avoid duplicate calls to validate the config files.

Was wondering if my logic makes sense, or if I should just add the config validation to the preflight checks?