update Solo to load remote config near entry point

[jeromy-cannon]

Currently the remote config is loaded usually after a commands initialize method. The problem here is that lease create is called at the top of the command and lease needs to know which cluster/context to create the lease on. In the case of multi-cluster, we will have multiple leases and multiple K8 instances (not implemented currently), so to avoid possible issues we need to load the remote config as close to the entry point of Solo as possible.

Solution:
In src/index.ts:main(argv: any) add a property that stores a function, similar to processArguments. This function will load the remote config. Then below the current .middleware(processArguments, false) add another middleware call for the function that will load the remote config.

Certain commands do not need to call K8 nor load the remote config. We should check the argv and not load the remote config in these conditions.

• if help is called, -h, --help
• if version is called, -v, --version
• if it is command init
• if it is command node and subcommand keys

Then remove all of the existing calls that load the remote config.

[Ivo-Yankov]

Not related to this issue, but isn't it better to have --version be a separate command instead of a flag?

[jeromy-cannon]

Not related to this issue, but isn't it better to have --version be a separate command instead of a flag?

I think it is directly integrated into yargs. I don't think we added it.

[swirlds-automation]

🎉 This issue has been resolved in version 0.34.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀