Deployment file

Catapult can read deployment options (E.g. the ones from Experimental deployments, or Deploy an scf helm chart from a URL ) directly from JSON config files.

The config file is read and it is translated to environment variables, which are then available in all the following Catapult make targets.

A deployment file defines the Catapult options (scf chart version, storageclass, features) and the scenario of the cluster or scf. This mechanism can be used also to propagate environment variables in all the Catapult steps.

This allows to replicate and store environmental settings, for example:

$> cat cap1.3.0.json
{
  "SCF_HELM_VERSION": "2.14.5",
  "CLUSTER_NAME": "cap1.3.0", 
  "ENABLE_EIRINI": "false",
  "DEFAULT_STACK": "cflinuxfs3"
}
$> CONFIG=$PWD/cap1.3.0.json BACKEND=backend make scf-deploy [..]

CONFIG is the environment variable which defines the (full) path to the config file. Environment variables have precedence over the one specified in the deployment file.

Note: the BACKEND annotation in the deployment file will be ignored, as it is required in earlier preparation steps. It is strongly adviced to annotate it anyway in the deployment file.