Empty custom mapping file aborts CLI commands - VMware Tanzu Spring Application Advisor

Products

• VMware Tanzu Spring Runtime

Issue/Introduction

Executing build-config get or upgrade-plan get fails completely when an empty or invalid custom mapping file is loaded. The CLI aborts the run and displays the following generic error message:

 com.vmware.tanzu.spring.advisor.exceptions.ControlledException: One of the custom mappings provided is empty

 

The error does not identify which specific mapping file causes the failure, making troubleshooting difficult.

Environment

• Product: VMware Tanzu Spring Application Advisor

• Component: Application Advisor CLI

• Versions: 1.6.x (Versions prior to 1.6.7)

Cause

The CLI encounters an empty or invalid custom mapping file (such as {}) during the configuration load phase. Instead of skipping the invalid file and continuing the operation, the tool throws a hard exception that halts the entire command.

Resolution

Update the CLI (Recommended)

Upgrade the Application Advisor CLI to version 1.6.7 or later. Starting in version 1.6.7, empty custom mappings are tolerated, allowing commands like build-config get to succeed. Note that the CLI skips the empty mapping silently without printing a warning identifying the file.  

 

Manual Workaround

If upgrading is not immediately possible, identify and remove the empty mapping file manually to unblock the run.

1. Navigate to the configured custom mappings directory (for example, ####/.advisor/mappings/).
2. Inspect the .json files to identify any that are completely empty or improperly formatted.
3. Delete or manually correct the offending file.
4. Re-run the build-config get or upgrade-plan get command.