anchor.diff:      * `SERVER-NAME` is the name for your config server.  
       * `CONFIG-FILE` is the filename of your server config json file.  
   
  -## <a id='bind-service'></a> Bind the Config Service to Your App Using Your Manifest
  -
  -The newly created config server must be bound to your app to be used by the app.
  -
  -1. To bind your config server to your app, add a new `services` section to your config server manifest file using the following format
  -
  -    ```yaml
  -    applications:
  -    - name: APP-NAME
  -      stack: windows
  -      buildpacks:
  -      - https://github.com/cloudfoundry-community/web-config-transform-buildpack/releases/download/VERSION/web-config-transform-buildpack-VERSION.zip
  -      - hwc_buildpack
  -      env:
  -        "SETTING-NAME": "SETTING-VALUE"
  -
  -      services:
  -      - SERVER-NAME     
  -    ```
  -
  -    Where:  
  -    * `APP-NAME` is your app's name.  
  -    * `VERSION` is the buildpack version.  
  -    * `SETTING-NAME` is the name of a configuration 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.   
  -    
       For example:
   
  -    ```yaml
  -    ---
  -    applications:
  -    - name: sampleapp
  -      stack: windows
  -      buildpacks: 
  -        - https://github.com/cloudfoundry-community/web-config-transform-buildpack/releases/download/v1.1.5/Pivotal.Web.Config.Transform.Buildpack-win-x64-1.1.5.zip
  -        - hwc_buildpack
  -      env:
  -        "connectionStrings:MyDB": "Data Source=ReleaseSQLServer;Initial Catalog=MyReleaseDB;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3"
  -
  -      services:
  -      - my_configserver
  -    ```
  -
  -## <a id='parameterize'></a> Parameterize the Manifest Environment Name
  -
  -Parameterizing your application environment settings gives you the ability to provide 
  -different environment configuration values for each deployment stage along your CD pipeline.   
  -
  -The Web Config Transform Extension Buildpack injects externalized Web.config  
  -appSettings and connectionString values into your container.  
  -
  -To parameterize your manifest:
  -
  -1. [Create Parameter Value Files](#parameter-value-files)
  -1. [Parameterize the Manifest File](#parameterize-manifest)
  -
  -### <a id='parameter-value-files'></a> Create Parameter Value Files  
  -
  -Your externalized Web.config files are stored in your gitHub repository as YAML files.  
  -
  -<p class='note'><strong>Note:</strong> Name your externalized Web.config YAML files to reflect their purpose, 
  -  such as <code>YOUR-APP-NAME.Development.yml</code>, <code>YOUR-APP-NAME.QA.yml</code>, 
  -  <code>YOUR-APP-NAME.UAT.yml</code>, or <code>YOUR-APP-NAME.Production.yml</code>.  
  -</p>
  -
  -* To externalize development appSettings and connectionString values, complete the following steps:  
  -    1. Create a new YAML config file named `YOUR-APP-NAME.Development.yml`.
  -    1. Modify the file with 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. Copy the `YOUR-APP-NAME.Development.yml` externalized configuration file to your GitHub repository.  
  -
  -    
  -* To externalize production appSettings and connectionString values, complete the following steps:  
  -    1. Create a new YAML config file named `YOUR-APP-NAME.Production.yml`.
  -    1. Modify the file with 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.Production.yml` externalized configuration file to your GitHub repository.  
  -
  -### <a id='parameterize-manifest'></a> Parameterize the Manifest File
  -
  -Your manifest file must be modified to read values from your externalized gitHub repository values.
  -
  -1. To parameterize your environment string, replace your manifest's hardcoded `env` value with `ASPNETCORE_ENVIRONMENT: ((env))` as follows:  
  +    <pre class="terminal">
  +    $ cf create-service p.config-server standard my_configserver  -c .\config-server.json
  +    </pre>
  +
  +### <a id='parameterize-manifest'></a> Configure Your App Manifest File for Spring Cloud Server
  +
  +Your app manifest file must be modified so it accepts configuration values from your externalized gitHub repository values.
  +
  +1. Backup your app manifest file.  
  +
  +1. To parameterize your environment string, replace your manifest's hardcoded `env` value with `ASPNETCORE_ENVIRONMENT: ((env))` using the following format:  
  +
  +    ```yaml
  +    env:
  +      ASPNETCORE_ENVIRONMENT: ((env))     
  +    ```
  +
  +1. To bind your config server to your app, add a new `services` section to your app manifest file 
  +using the following format:
  +
  +    ```yaml
  +    services:
  +    - SERVER-NAME     
  +    ```
  +
  +    Where `SERVER-NAME` is the name for your config server.  
  +<br>
  +
  +1. Review the resulting manifest file. The manifest file should adhere to the following format:
       
       ```yaml
       applications:
  
positive.code:       Setting1: "Common setting1"  
        ```
  
  1. Create separate YAML files for each unique environment to hold your environment-specific settings.  
  <br>
      Name the files `YOUR-APPLICATION`-`APP-ENVIRONMENT`.yaml.  
  <br>
      Where:  
      * `YOUR-APPLICATION` is the identifier name for your application.  
  
negative.code:     cf push
      ```
  
  ## <a id='move-to-spring-cloud'></a> Establish a Spring Cloud Config Server 
  
  You must store your environment-specific transformations in a secured environment for your deployment to be production-ready.  
  
  A multi-environment, production-ready deployment configuration can be achieved by using Spring Cloud Config Server 
  backed by transforms stored in a git repository data source.
  
  ### <a id='create-for-spring-cloud'></a> Create Configurations for Spring Cloud Config Server
  
  To create transformations for use by Spring Cloud Config Server, complete the following steps:   
  
  1. Determine the name you are using for your environment. For example you could be creating a "Development", "Debug" or "Production" manifest.
      <p class='note'><strong>Note:</strong> You will use this name for both the file you create in this task as well as
      in your manifest file's <code>ASPNETCORE_ENVIRONMENT</code> environment variable value.
      </p>
  
  1. Create a YAML file to hold your common settings across all environments. 
  Name the file `YOUR-APPLICATION`.yaml.  
  <br>
      Where `YOUR-APPLICATION` is the identifier name for your application.  
  <br>
  