misleading error handling when yaml declaration cannot be validated

[amolari]

Issue: error handling if the yaml declaration is not correctly loaded

While the yaml declaration may pass validation on some popular Internet yaml validators (copy/paste), it may goes in error when loaded with

f5-bigip-runtime-init/src/cli.ts

Line 50 in 3c85a64

config = yaml.safeLoad(fs.readFileSync(program.configFile, 'utf8'));

Example: a tab instead of spaces in the declaration

After the changes made here:
d805e9a#diff-fa8d4e24d8399e8350f1c8bad05df53e8032ea995835bf911507015e2db61cdd

the process is to load the declaration as a json if the yaml safeload went in error. That will of course produce an error, which can be confusing.
If the yaml safeload went in error, an explicit error indicating the yaml validation issue (eventually not blocking, if you want to try to load the config as json) should be thrown in the log.

[shyawnkarim]

Thanks for reporting this issue. We are now tracking this internally with ID ESECLDTPLT-2548.