anchor.diff:      }
     ],
     "labels": { <4>
  -    "custom_label": "custom_label_value"
  +    "custom_label": "Label_Name"
     },
     "items": [ <5>
       {
  
positive.code: <4> A list of labels to apply to resources
  <5> A list of resources to create
  
  == Labels
  The list of labels specified in the template will be applied to every resource that is generated from the template. link:../architecture/kubernetes_model.html#label[Labels] can be used to manage and organize generated resources.
  
  == Parameters
  The list of parameters that you want to override are listed in the *parameters* section of the template. Alternatively, you can override them with the following command, specifying the file to be used:
  
  ****
  `osc process --parameters -f [replaceable]#<filename>#`
  ****
  
  The following shows the output when listing the parameters for one of the [replaceable]#openshift/origin/examples# template.
  
  .Example Template Output
  ====
  ----
  $ osc process --parameters -f examples/sample-app/application-template-dockerbuild.json
  NAME                  DESCRIPTION              GENERATOR           VALUE
  
negative.code: MYSQL_ROOT_PASSWORD   database password        expression          [a-zA-Z0-9]{8}
  MYSQL_DATABASE        database name                                root
  ----
  
  ====
  
  The output identifies several parameters that are generated with a regex expression generator when the template is processed.
  
  == Generating a Configuration
  When OpenShift processes a template, it creates a configuration. You can override the parameters with the values defined in the configuration file by adding the appropriate flags.
  
  Generate a configuration with the following command:
  
  ****
  `osc process -f _<filename>_`
  ****
  
  Continuing with the previous example, you can override the *`ADMIN_USERNAME`* and *`MYSQL_DATABASE`* environment variables to create a JSON string to apply to the server. The JSON string represents a configuration with customized environment variables, as shown in the following example.
  
  .Generating a Configuration
  ====
  
  ----
  $ osc process -f examples/sample-app/application-template-dockerbuild.json -v ADMIN_USERNAME=root,MYSQL_DATABASE=admin
  ----
  
  ====
  
  The JSON string can either be redirected to a file or applied directly by piping the process output to the `apply` command, as shown in the following example.
  
  .Redirecting JSON String
  ====
  
  ----
  $ osc process -f examples/sample-app/application-template-dockerbuild.json -v ADMIN_USERNAME=root,MYSQL_DATABASE=admin | osc apply -f -
  ----
  
  ====
  