Adding and Editing Inline Tanzu Manifest Files

Updated 1 month ago by Chakravarthy Tenneti

Manifests provide consistency and reproducibility, and help automate in deploying apps. For more information about manifest files, see Deploying with Application Manifest from Tanzu.

When you create the Tanzu Application Service (TAS, formerly PCF) Service in Harness, the Manifests section is created and the default manifest.yml and vars.yml files are added.

The use of PCF in the default manifest.yml and vars.yml file is because TAS was formerly PCF.

In this topic:

Before You Begin

Visual Summary

Here is an example showing how the variables in manifest.yml are given values in vars.yml:

You can also use variables for partial values. For example, you can specify host in your vars.yml file and - route: ((host)).env.com in your manifest.yml file.

TAS Manifest deployments are a common TAS strategy. You can learn more about it in Deploying with App Manifests from TAS.

Harness supports all of the typical features of TAS manifests, as described in Deploying with App Manifests from TAS, but to deploy multiple apps, you will need to use multiple Harness Services.

Step 1: Edit vars.yaml file

This file contains the following default variables and values:

  • PCF_APP_NAME: ${app.name}__${service.name}__${env.name}
  • PCF_APP_MEMORY: 750M
  • INSTANCES: 1

These are referenced in the manifest.yaml file.

Change the TAS App Name

You can change the TAS app name here if you do not want Harness to generate one using a concatenation of the Harness Application, Service, and Environment names (${app.name}__${service.name}__${env.name}).

You can add more variables in vars.yaml and override them as described in Using Harness Config Variables in Tanzu Manifests.

Step 2: Edit manifest.yml file

Define the default name, memory limit, and number of instances.

You can override variable values such as ((PCF_APP_NAME)), ((APP_MEMORY)), and ((INSTANCES)) in the vars.yml file.

Next Steps


How did we do?