anchor.diff:      ```
   
       <p class='note'><strong>Note:</strong> Adding token replacements with Environment variables is only for experimental activities. 
  -    Only put configuration item keys and values in the manifest for testing purposes. 
  -    Config settings should be externalized using git repositories and Spring Cloud Config Server. 
  -    Spring Cloud Config Server should be used for externalizing configuration settings. 
  -    For more information about externalizing configuration settings in Spring Cloud Config Server, see <a href="#move-to-spring-cloud">Move Config Settings to Spring Cloud Config Server</a>, below.
  +    The manifest should contain configuration item keys and values for testing purposes only. 
  +    Configuration settings should be externalized using git repositories and Spring Cloud Config Server.  
  +    For more information about externalizing configuration settings in Spring Cloud Config Server, 
  +    see <a href="#move-to-spring-cloud">Move Configuration Settings to Spring Cloud Config Server</a>, below.
       </p>
   
  -## <a id='test-push'></a> Validation Test the App
  +### <a id='test-push'></a> Validation Test the App
   
   1. Build and push the app to Cloud Foundry to verify that your config settings are properly transformed by running the following command:   
   
  
positive.code: 
  ## <a id='parameterize'></a> Parameterize the Manifest Environment Name
  
  Parameterizing your application environment gives ability to provide different values 
  depending on your current deployment stage along your CD pipeline.  
  
  To parameterize your manifest:
  
  1. [Create Parameter Value Files](#parameter-value-files)
  1. [Parameterize the Manifest File](#parameterize)
  
  ### <a id='parameter-value-files'></a> Create Parameter Value Files
  
  You can externalize your Web.config file's appSettings and connectionString values 
  in files stored in your gitHub repository. 
  
  1. To externalize development appSettings and connectionString values include the values, create a new file
   YAML config file named `YOUR-APP-NAME.development.yml` containing the following content:  
  
      ```yaml
      appSettings:
        SETTING-NAME: "SETTING-VALUE"
        SETTING-NAME: "SETTING-VALUE"
       connectionStrings:
         MyDB: "Data Source=SERVER-NAME;Initial Catalog=DB-NAME;User ID=ACCOUNT-ID;Password=PASSWORD"
      ```
  
      Where:  
      * `SETTING-NAME` is the name of a setting used by your app. Create as many NAME : "VALUE" pair lines as are needed by your app.  
      * `SETTING-VALUE` is the development value of the setting. Create as many NAME : "VALUE" pair lines as are needed by your app.  
      * `SERVER-NAME` is the name for your development database server.  
      * `DB-NAME` is the name for your development database.  
      * `ACCOUNT-ID` is the is the development service account name.  
      * `PASSWORD` is the development service account password.  
      
  1. To externalize production appSettings and connectionString values include the values, create a new file
   YAML config file named `YOUR-APP-NAME.production.yml` containing the following content:  
  
      ```yaml
      appSettings:
        SETTING-NAME: "SETTING-VALUE"
        SETTING-NAME: "SETTING-VALUE"
       connectionStrings:
         MyDB: "Data Source=SERVER-NAME;Initial Catalog=DB-NAME;User ID=ACCOUNT-ID;Password=PASSWORD"
      ```
  
      Where:  
      * `SETTING-NAME` is the name of a setting used by your app. Create as many NAME : "VALUE" pair lines as are needed by your app.  
      * `SETTING-VALUE` is the production value of the setting. Create as many NAME : "VALUE" pair lines as are needed by your app.  
      * `SERVER-NAME` is the name for your production database server.  
      * `DB-NAME` is the name for your production database.  
      * `ACCOUNT-ID` is the is the production service account name.  
      * `PASSWORD` is the production service account password.  
  
  1. Copy the `YOUR-APP-NAME.development.yml` and `YOUR-APP-NAME.production.yml` externalized configuration files to your GitHub repository.  
  
  ### <a id='parameterize'></a> Parameterize the Manifest File
  
  e.g: Development/QA/UAT/Production.
  
  1. To parameterize your environment string, replace your manifest's hardcoded `env` value with `ASPNETCORE_ENVIRONMENT: ((env))` as follows:  
      
  
negative.code:     cf push
      ```
  
  ## <a id='move-to-spring-cloud'></a> Move Configuration Settings to Spring Cloud Config Server 
  
  A multi-environment, production-ready configuration can be achieved using Spring Cloud Config Server 
  backed by environment-specific transforms anda git repository data source.
  
  1. Determine your manifest file's `ASPNETCORE_ENVIRONMENT` environment variable value.  
  1. Create a network accessible git repository for each application.  
  