Handle optional JSON configuration files
Some JSON configuration files may be optionally defined, therefore this
needs to be handled when retrieving the file or loading it. When a JSON
configuration file is marked as optional and no file is found, an empty
filesystem path is returned.
Tested:
No change to current use of getting/loading JSON configuration files
Empty filesystem path is returned for an optional file not found
Only an existing JSON config files are loaded
Change-Id: I2b5c632df6df1f4cff5249be4d01c1376e0a3482
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
1 file changed