Adding and Editing Inline PCF Manifest Files
When you create the PCF Service, the Manifests section is created and the default manifest.yml and vars.yml files are added.
In this topic:
- Before You Begin
- Visual Summary
- Step 1: Edit values.yaml file
- Step 2: Edit deployment.yaml file
- Next Steps
Before You Begin
Here is an example showing how the variables in manifest.yml are given values in vars.yml:
hostin your vars.yml file and
- route: ((host)).env.comin your manifest.yml file.
PCF Manifest deployments are a common PCF strategy. You can learn more about it in Deploying with App Manifests from Pivotal.
Harness supports all of the typical features of PCF manifests, as described in Deploying with App Manifests from Pivotal, but to deploy multiple apps, you will need to use multiple Harness Services.
Step 1: Edit values.yaml file
This file contains the data for templated files in Manifests, using the Go text template package.
The only mandatory file and folder requirement in Manifests is that values.yaml is located at the directory root. The values.yaml file is required if you want to use Go templating. It must be named values.yaml and it must be in the directory root.
Step 2: Edit deployment.yaml file
This manifest contains three API object descriptions, ConfigMap, Secret, and Deployment. These are standard descriptions that use variables in the values.yaml file.
Manifest files added in Manifests are freeform. You can add your API object descriptions in any order and Harness will deploy them in the correct order at runtime.
Add or edit these default files as needed.