Initialization fails when auth file invalid or errored

[f1ames]

Initializing extension will fail there is an issue with auth.yaml file reading.

It may happen when there is an error reading it or auth format change. The 2nd happened between 0.2.0 and 0.3.0 version, and the extension would fail to initialize for anyone who had been authenticated (meaning auth file present) and updated to 0.3.x.

Happened to @WitoDelnat with Activating extension ‘Kubeshop.monokle’ failed: Cannot read properties of undefined (reading ‘access_token’). error.

---

This means there is error handling missing somewhere, most probably during Authenticator initialization (which reads auth file) in:

• vscode-monokle/src/utils/authentication.ts

  Line 14 in 404fcae

  return createDefaultMonokleAuthenticator();

• and https://github.com/kubeshop/monokle-core/blob/c2ff20e852608c08423ae26aa001e61ef6631b3c/packages/synchronizer/src/utils/authenticator.ts#L32

[WitoDelnat]

I managed to get the extension working again after deleting the old auth.yaml file. I guess it's not the highest priority given that most users will have started at the >v3.