What problem are you trying to solve?

As part of the config file v2 rollout, I need to be able to detect if a local configuration file is v1 or v2 and adjust control flow accordingly (until the config merge endpoint on the backend can be updated, the analyzer needs to error when handling a v2 config).

get_config has highly-nested control flow, making this difficult to do in an understandable way.

What is your solution?

• Flatten the control flow using more idiomatic Rust.
• Read the file once as a String, and then parse to ConfigFile or convert to base64 from that String

What the reviewer should know

• This function can no longer panic: the usage of expect was replaced with proper Result propagation (anyhow::Context).