om configure-product fails with 'unrecognized keys: deploy-in-parallel'

Products

• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

When running automation pipelines (e.g., Concourse CI) to configure a product tile using the om CLI, the task fails with the following error message:

2026/06/03 07:10:33 the config file contains unrecognized keys: deploy-in-parallel

This typically occurs after upgrading to VMware Tanzu Operations Manager v3.3+ or Tanzu Application Service (TAS) v10.4+, where the deploy-in-parallel property is introduced in the staged configuration.

Environment

VMware Tanzu Platform - Cloud Foundry

Cause

The deploy-in-parallel property is a new configuration key introduced in recent versions of Ops Manager to support parallel tile deployments.

While newer versions of the om CLI (v7.21.x+) correctly export and recognize this key during the staged-config and configure-product commands, older versions of the CLI do not have this key in their validation schema. When the automation attempts to re-apply a configuration file containing this key using an outdated CLI, the validation fails because the key is "unrecognized."

Resolution

To resolve this issue, you must update the om CLI binary used in your automation environment.

Step 1: Verify Current Version

Check the version of the om CLI running in your automation pipeline

om --version

If the version is 7.20.1 or earlier, it will not recognize the deploy-in-parallel key.

Step 2: Upgrade to v7.21.x+

Download and install om CLI version 7.21.0 or later from the github or your internal artifact mirror.

If you are using the Platform Automation Toolkit, ensure you are using a recent task image that includes om v7.21.x.

Step 3: (Workaround) Manual Configuration Cleanup

If you cannot immediately upgrade the CLI, you can manually remove the offending key from your configuration YAML before running the configure command:

1. Open your interpolated product configuration file (e.g., cf-staged-config.yml).
2. Locate the line: deploy-in-parallel: #### (where #### is true or false).
3. Delete this line and save the file.
4. Re-run the om configure-product command.