update for AEM-supported xrefs

Author: anita-flegg

docs/how-to-guides/_getting-started.html.md.erb

@@ -293,7 +293,7 @@ and to current and future teammates and collaborators.</p>
 
 #### <a></a> The test task
 
-Platform Automation Toolkit comes with a [`test`](../tasks.md#test) task you
+Platform Automation Toolkit comes with a [`test`](../tasks.html#test) task you
 can use to validate that it's been installed correctly.
 
 1. Add the following to your `pipeline.yml`, starting on the line after the `---`:

docs/how-to-guides/adding-a-product.html.md.erb

@@ -39,7 +39,7 @@ The instructions and example in the following add the [VMware Tanzu Application
 
 ### Download
 
-Before setting the pipeline, create a config file for [`download-product`](../tasks.md#download-product)
+Before setting the pipeline, create a config file for [`download-product`](../tasks.html#download-product)
 to download Tanzu Application Service from the Broadcom Support portal.
 
 Create a `download-tas.yml` file for the IaaS you are using.
@@ -113,7 +113,7 @@ you can add a new `download-upload-and-stage-tas` job in your `pipeline.yml` fil
 4. If fly set-pipeline returns an error,
 fix any and all errors until the pipeline can be set.
 When the pipeline can be set properly, run:
-        
+
     ```
     git add pipeline.yml
     git commit --amend --no-edit
@@ -228,7 +228,7 @@ You can still go through this process without an initial applying changes,
 but you will be unable to use <code>om staged-config</code> with <code>--include-credentials</code>,
 and may have an incomplete configuration at the end of this process.</p>
 
-[`om`](https://github.com/pivotal-cf/om) has a command called [staged-config](../tasks.md#staged-config).
+[`om`](https://github.com/pivotal-cf/om) has a command called [staged-config](../tasks.html#staged-config).
 It is used to extract staged product
 configuration from the Tanzu Operations Manager UI.
 `om` requires a `env.yml`, which is available. It was used in the `upload-and-stage` task.
@@ -628,7 +628,7 @@ outlined in these examples is `config-template`.
 `config-template` is an `om` command that creates a base config file with optional ops files
 from a given tile or pivnet slug.
 
-This section assumes that you are adding 
+This section assumes that you are adding
 [TAS for VMs](https://support.broadcom.com/group/ecx/productdownloads?subfamily=VMware%20Tanzu%20Application%20Service%20for%20VMs),
 as in the procedure above.
 
@@ -700,7 +700,7 @@ here are some approaches you can use:
 - Look at the tile's online documentation
 - Upload the tile to a Tanzu Operations Manager
   and visit the tile in the Tanzu Operations Manager UI to see if that provides any hints.
-  
+
     If you are still struggling, inspect the HTML of the Tanzu Operations Manager web page
     to help you map the value names to the associated UI elements.
 

docs/how-to-guides/creating-a-director-config-file.html.md.erb

@@ -14,13 +14,13 @@ For detailed instructions, see [Installing Tanzu Operations Manager](./installin
 
 ## Extracting configuration
 
-In [om](https://github.com/pivotal-cf/om) there is a command called [staged-director-config](../tasks.md#staged-director-config), which is used to extract
+In [om](https://github.com/pivotal-cf/om) there is a command called [staged-director-config](../tasks.html#staged-director-config), which is used to extract
 the Tanzu Operations Manager and the BOSH director configuration from the targeted foundation.
 
 <%= partial "../missing_fields_opsman_director" %>
 
-Sample usage:  
-`om --env env.yml staged-director-config > director.yml`  
+Sample usage:
+`om --env env.yml staged-director-config > director.yml`
 
 This gives you the whole configuration of Tanzu Operations Manager in a single YAML file.
 It will look more or less the same as the example above. You can check it
@@ -36,10 +36,10 @@ after running this command:
 Now you can modify the settings in the configuration file directly instead of
 operating in the Web UI. After you finish editing the file, the configuration
 file will need to be applied back to the Tanzu Operations Manager instance. The command
-[configure-director](../tasks.md#configure-director) will do the job.
+[configure-director](../tasks.html#configure-director) will do the job.
 
-Sample usage:  
-`om --env env.yml configure-director --config director.yml`  
+Sample usage:
+`om --env env.yml configure-director --config director.yml`
 
 
 ## Promoting Tanzu Operations Manager to another foundation
@@ -67,7 +67,7 @@ and they change the default behavior if they are defined.
 Use with caution.
 
 In the following example, two new VM extensions are defined
-and will be added to the list of available extensions on the next [`configure-director`](../tasks.md#configure-director).
+and will be added to the list of available extensions on the next [`configure-director`](../tasks.html#configure-director).
 This can be added to the end of your existing `director.yml`,
 or defined independently and set with no other configurations present.
 
@@ -111,7 +111,7 @@ and they change the default behavior if they are defined.
 Use with caution.
 
 In the following example, two new VM types are defined
-and will be added to the list of available types on the next [`configure-director`](../tasks.md#configure-director).
+and will be added to the list of available types on the next [`configure-director`](../tasks.html#configure-director).
 This can be added to the end of your existing `director.yml`,
 or defined independently and set with no other configurations present.
 

docs/how-to-guides/git-repo-layout.html.md.erb

@@ -163,7 +163,7 @@ There are many possibilities for structuring Git repos in complex situations.
 For guidance on how to best set up your git's file structure,
 see [Inputs and outputs](../inputs-outputs.md).
 Take note of the `inputs` and `outputs` of the
-various [Platform Automation Toolkit tasks](../tasks.md).
+various [Platform Automation Toolkit tasks](../tasks.html).
 As long as the various input / output mappings correctly correlate
 to the expected inputs and outputs of the Platform Automation Toolkit tasks,
 any file structure could theoretically work.

docs/how-to-guides/installing-opsman.html.md.erb

@@ -15,7 +15,7 @@ Do this by changing:
    - the `name` of the task
    - the `file` of the task
 
-    The first task in the job should be [`download-product`](../tasks.md#download-product).
+    The first task in the job should be [`download-product`](../tasks.html#download-product).
     It has an additional required input;
     the `config` file `download-product` uses to talk to the Broadcom Support portal.
 
@@ -141,7 +141,7 @@ for creating a deploy key.
     <%= partial include './paths-and-pipeline-names' %>
 
 1. To perform interpolation in one of your input files,
-use the [`prepare-tasks-with-secrets` task](../tasks.md#prepare-tasks-with-secrets).
+use the [`prepare-tasks-with-secrets` task](../tasks.html#prepare-tasks-with-secrets).
 In earlier steps, you relied on Concourse's native integration with CredHub for interpolation.
 That worked because you needed to use the variable
 in the pipeline itself, not in one of our inputs.
@@ -175,7 +175,7 @@ in the pipeline itself, not in one of our inputs.
             tasks: platform-automation-tasks
           params:
             CONFIG_PATHS: config
-        - task: download-product        
+        - task: download-product
           image: platform-automation-image
           file: platform-automation-tasks/tasks/download-product.yml
           params:
@@ -248,7 +248,7 @@ Follow these steps to use the `paving` repository:
     # cp -Ra paving/${IAAS} paving-${IAAS}
     mkdir paving-${IAAS}
     cp -a paving/$IAAS/. paving-$IAAS
-    cd paving-${IAAS} 
+    cd paving-${IAAS}
     ```
 
     `IAAS` must be set to match one of the infrastructure directories
@@ -288,7 +288,7 @@ Follow these steps to use the `paving` repository:
     ```bash
     terraform apply \
       -parallelism=5 \
-      terraform.tfplan 
+      terraform.tfplan
     ```
 
 8. Save the output from `terraform output stable_config`
@@ -364,7 +364,7 @@ you can add the new task to the `install-opsman` job.
             tasks: platform-automation-tasks
           params:
             CONFIG_PATHS: config
-        - task: download-product        
+        - task: download-product
           image: platform-automation-image
           file: platform-automation-tasks/tasks/download-product.yml
           params:
@@ -526,7 +526,7 @@ and the placeholder state file.
             tasks: platform-automation-tasks
           params:
             CONFIG_PATHS: config
-        - task: download-product        
+        - task: download-product
           image: platform-automation-image
           file: platform-automation-tasks/tasks/download-product.yml
           params:
@@ -549,7 +549,7 @@ and the placeholder state file.
     Because <code>opsman.yml</code> is the default input to
     <code>OPSMAN_CONFIG_FILE</code>, it is redundant
     to set this param in the pipeline.
-    See the <a href="../tasks.md">Task reference</a>
+    See the <a href="../tasks.html">Task reference</a>
     available and default parameters.</p>
 
 1. Now set the pipeline.
@@ -583,7 +583,7 @@ and the placeholder state file.
             tasks: platform-automation-tasks
           params:
             CONFIG_PATHS: config
-        - task: download-product        
+        - task: download-product
           image: platform-automation-image
           file: platform-automation-tasks/tasks/download-product.yml
           params:

docs/how-to-guides/setting-up-s3.html.md.erb

@@ -208,7 +208,7 @@ You should probably **_not_** store the following in S3:
 - `secrets.yaml` environment and secret files - There are a number of ways
 to handle these types of files, but they should not be stored in S3.
 See [Using a secrets store to store credentials](../concepts/secrets-handling.md)
-for information about working with these types of files.  
+for information about working with these types of files.
 
 ## Structuring your bucket
 
@@ -238,7 +238,7 @@ The following sample shows one way to set up your bucket file structure:
 
 When viewing a bucket in the AWS S3 console,
 click **Create Folder**.
-To create a sub-folder, select **Create Folder** again.  
+To create a sub-folder, select **Create Folder** again.
 
 When attempting to access a specific object in a folder,
 include the folder structure before the object name:
@@ -274,7 +274,7 @@ and where to find more information.
 
 #### The download-product task
 
-The [`download-product`](../tasks.md#download-product) task lets you download products from the Broadcom Support portal.
+The [`download-product`](../tasks.html#download-product) task lets you download products from the Broadcom Support portal.
 If S3 properties are set in the [download config](../inputs-outputs.md#download-product-config),
 these files can be put into an S3 bucket.
 
@@ -320,7 +320,7 @@ For example, for a product with slug of <code>product-slug</code> and version of
 </code>
 </p>
 
-The [`download-product`](../tasks.md#download-product)
+The [`download-product`](../tasks.html#download-product)
 task lets you download products from an blobstore bucket if you define the `SOURCE` param.
 The prefixed metadata added by `download-product` with `SOURCE: pivnet` is used to find the appropriate file.
 This task uses the same [download-product config file](../inputs-outputs.md#download-product-config)
@@ -333,4 +333,4 @@ to be used together.
 The download product config should be different between the two tasks.
 
 For complete information on this task
-and how it works, see the [Task Reference](../tasks.md#download-product).
+and how it works, see the [Task Reference](../tasks.html#download-product).

docs/how-to-guides/upgrade-existing-opsman.html.md.erb

@@ -30,7 +30,7 @@ Do this by changing:
    - the `name` of the task
    - the `file` of the task
 
-    The first task in the job should be [`download-product`](../tasks.md#download-product).
+    The first task in the job should be [`download-product`](../tasks.html#download-product).
     It has an additional required input;
     the `config` file `download-product` uses to talk to the Broadcom Support portal.
 
@@ -179,7 +179,7 @@ you can add a resource to tell Concourse how to get it as `env`.
     <%= partial "./paths-and-pipeline-names" %>
 
 1. To perform interpolation in one of your input files,
-you need the [`credhub-interpolate` task](../tasks.md#credhub-interpolate)
+you need the [`credhub-interpolate` task](../tasks.html#credhub-interpolate)
 Earlier, you relied on Concourse's native integration with CredHub for interpolation.
 That worked because you needed to use the variable
 in the pipeline itself, not in one of your inputs.
@@ -337,7 +337,7 @@ it's time to create another Concourse job to do the upgrade itself.
 The export and the upgrade need to be in separate jobs
 so they can be triggered (and re-run) independently.
 
-This new job uses the [`upgrade-opsman`](../tasks.md#upgrade-opsman) task.
+This new job uses the [`upgrade-opsman`](../tasks.html#upgrade-opsman) task.
 
 1. Write a new job that has `get` steps
 for your platform-automation resources
@@ -393,7 +393,7 @@ it's a good place to start.
     This workflow makes it easy to keep what is set on Concourse
     and what is pushed to your source control remote in sync.</p>
 
-1. You need the three required inputs for [`upgrade-opsman`](..//tasks.md#upgrade-opsman).
+1. You need the three required inputs for [`upgrade-opsman`](../tasks.html#upgrade-opsman).
 
       * `state`
       * `config`
@@ -438,12 +438,12 @@ commit it, and push it:
     git push
     ```
 
-    You can map the `env` resource to the [`upgrade-opsman`](..//tasks.md#upgrade-opsman)
+    You can map the `env` resource to the [`upgrade-opsman`](../tasks.html#upgrade-opsman)
     `state` input after you add the task.
 
     But first, there are two more inputs to arrange for.
 
-1. Option 1: Write a [Tanzu Operations Manager VM Configuration file](../inputs-outputs.md#opsman-config)
+1. Option 1: Write a [Tanzu Operations Manager VM Configuration file](../inputs-outputs.html#opsman-config)
 to `opsman.yml`.
 The properties available vary by IaaS,
 but you can often inspect your existing Tanzu Operations Manager
@@ -749,7 +749,7 @@ in the directory it is called from.
     git push
     ```
 
-2. Get the image for the new Tanzu Operations Manager version using the [`download-product`](../tasks.md#download-product) task.
+2. Get the image for the new Tanzu Operations Manager version using the [`download-product`](../tasks.html#download-product) task.
 It requires a config file to specify which Tanzu Operations Manager to get,
 and to provide the Broadcom Support portal credentials.
 Name this file `download-opsman.yml`:
@@ -823,7 +823,7 @@ Name this file `download-opsman.yml`:
     <code>env.yml</code> is the default input to <code>ENV_FILE</code>,
     and <code>state.yml</code> is the default input to <code>STATE_FILE</code>,
     it is redundant to set this param in the pipeline.
-    See the <a href="../tasks.md">task definitions</a>
+    See the <a href="../tasks.html">task definitions</a>
     for a full range of the
     available and default parameters.</p>
 

docs/pipeline-design/configuration-management-strategies.html.md.erb

@@ -47,7 +47,7 @@ uses the "Single Repository for each Foundation" pattern:
 Notice that there is only one subdirectory
 and that all other files are in the base directory.
 This minimizes parameter mapping in the platform-automation tasks.
-For example, in the [`configure-director`](../tasks.md#configure-director)
+For example, in the [`configure-director`](../tasks.html#configure-director)
 step:
 
 ```yaml
@@ -110,7 +110,7 @@ The design considerations for this strategy, as implemented, are:
   It makes use of only concepts and workflows
   built in to Platform Automation and Concourse.
 - There are no significant differences between the required setup of the foundations.
-  
+
     This doesn't mean that this strategy cannot be used
     with more complicated differences.
     If the pipelines need to be different for one reason or another,
@@ -353,9 +353,9 @@ This feature is only available in Concourse 5+. The example that follows does no
 In certain circumstances, resources can be modified by one task in a job
 for use later in that same job. A few tasks that offer this ability include:
 
-- [credhub-interpolate](../tasks.md#credhub-interpolate)
-- [prepare-tasks-with-secrets](../tasks.md#prepare-tasks-with-secrets)
-- [prepare-image](../tasks.md#prepare-image)
+- [credhub-interpolate](../tasks.html#credhub-interpolate)
+- [prepare-tasks-with-secrets](../tasks.html#prepare-tasks-with-secrets)
+- [prepare-image](../tasks.html#prepare-image)
 
 For each of these tasks, `output_mapping` can be used to overwrite
 an input with a modified input for use with tasks later in that job.

docs/pipelines/multiple-products.html.md.erb

@@ -186,7 +186,7 @@ Platform Automation Toolkit will not create these resources for you.
 This secrets handling example helps load secrets stored in an external credential manager such as CredHub.
 Concourse support several [credential managers](https://concourse-ci.org/creds.html) natively.
 
-The configuration below uses the [`prepare-tasks-with-secrets`](../tasks.md#prepare-tasks-with-secrets) task
+The configuration below uses the [`prepare-tasks-with-secrets`](../tasks.html#prepare-tasks-with-secrets) task
 to load secrets from your external configuration files.
 
 ```yaml
@@ -319,7 +319,7 @@ jobs:
       VARS_FILES: |
         vars/foundations/((foundation))/vars/director.yml
         vars/foundations/((foundation))/vars/tas.yml
-        vars/foundations/((foundation))/vars/pks.yml 
+        vars/foundations/((foundation))/vars/pks.yml
   - task: apply-director-changes
     image: platform-automation-image
     attempts: 3
@@ -439,7 +439,7 @@ jobs:
       VARS_FILES: |
         vars/foundations/((foundation))/vars/director.yml
         vars/foundations/((foundation))/vars/tas.yml
-        vars/foundations/((foundation))/vars/pks.yml 
+        vars/foundations/((foundation))/vars/pks.yml
   - task: apply-director-changes
     image: platform-automation-image
     file: platform-automation-tasks/tasks/apply-director-changes.yml

docs/pipelines/resources.html.md.erb

@@ -25,7 +25,7 @@ and places them into a trusted s3-like storage provider.
 This helps other Concourse deployments without internet access
 retrieve task dependencies.
 
-The pipeline requires configuration for the [download-product](../tasks.md#download-product) task.
+The pipeline requires configuration for the [download-product](../tasks.html#download-product) task.
 See the following for examples that you can use.
 
 <p class="note important">
@@ -37,7 +37,7 @@ to accurately download files from a blobstore (for example, s3, gcs, azure),
 so the product slug and version are prepended when using <code>download-product</code>.
 For more information about how this works,
 and what to expect when using <code>download-product</code>,
-see the <a href="../tasks.md#download-product"><code>download-product</code> task reference</a></p>
+see the <a href="../tasks.html#download-product"><code>download-product</code> task reference</a></p>
 
 **Healthwatch**
 
@@ -138,7 +138,7 @@ resource_types:
 
 ### Product resources
 
-These are the S3 resources where Platform Automation Toolkit [`download-product`](../tasks.md#download-product) outputs will be stored.
+These are the S3 resources where Platform Automation Toolkit [`download-product`](../tasks.html#download-product) outputs will be stored.
 Each product/stemcell needs a separate resource defined.
 Platform Automation Toolkit will not create these resources for you.
 
@@ -304,7 +304,7 @@ For more details, see [Inputs and outputs](../inputs-outputs.md).
 This example shows how to load secrets stored in an external credential manager such as CredHub.
 Concourse supports several [credential managers](https://concourse-ci.org/creds.html) natively.
 
-The configuration below uses the [`prepare-tasks-with-secrets`](../tasks.md#prepare-tasks-with-secrets) task
+The configuration below uses the [`prepare-tasks-with-secrets`](../tasks.html#prepare-tasks-with-secrets) task
 to load secrets from your external configuration files.
 
 ```yaml