add Last Modified Date to each topic [#157705816]

animatedmax · animatedmax · commit 9e47fc1d37a4 · 2018-05-29T14:37:35.000-07:00
diff --git a/bosh-release.html.md.erb b/bosh-release.html.md.erb
@@ -3,6 +3,8 @@ title: BOSH Releases
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic provides resources for creating a BOSH release that integrates a software service with Pivotal Cloud Foundry (PCF) at the managed service level.
 
 ## <a id="overview"></a> Overview
diff --git a/brokered.html.md.erb b/brokered.html.md.erb
@@ -3,6 +3,8 @@ title: Brokered Service
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 The topics in this subsection explain how to integrate your software service with Pivotal Cloud Foundry (PCF) to create a brokered service and service tile for PCF.
 
 ## <a id="overview"></a> Overview
diff --git a/buildpacks.html.md.erb b/buildpacks.html.md.erb
@@ -3,6 +3,8 @@ title: Buildpacks
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 Buildpacks compile and package apps to run on PCF. This topic lists resources for using and deploying buildpacks with PCF apps, and for creating your own custom buildpack.
 
 ## <a id="language"></a> Official Buildpacks
diff --git a/cf-concepts.html.md.erb b/cf-concepts.html.md.erb
@@ -3,6 +3,8 @@ title: How PCF and PCF Services Work
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 There are many ways to integrate services with Pivotal Cloud Foundry (PCF). The right one for each service depends on what the service does, and how
 customer applications consume it. To determine the best way to integrate your
 service, you'll need a good understanding of PCF concepts like applications, containers, services, brokers, and buildpacks.
diff --git a/concourse.html.md.erb b/concourse.html.md.erb
@@ -3,6 +3,8 @@ title: Continuous Integration Testing
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to use the [Tile Dashboard](https://tile-dashboard.cfapps.io/static/index.html#/environments) continuous integration (CI) system and its underlying [Concourse](http://concourse.ci) platform to help develop and integrate software services for Pivotal Cloud Foundry (PCF).
 
 ## <a id="tile-dashboard-ci"></a> Tile Dashboard CI
diff --git a/contacts.html.md.erb b/contacts.html.md.erb
@@ -3,6 +3,8 @@ title: Contact Us
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 To learn more about the Pivotal ISV Partner Program, or to request
 our assistance with your integration project, please contact us at
 one of the following addresses:
diff --git a/create-credhub-vars.html.md.erb b/create-credhub-vars.html.md.erb
@@ -3,6 +3,8 @@ title: Creating New Variables in CredHub
 owner: CredHub
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how CredHub manages variables in the context of a larger deployment, and how to create new variables for use in CredHub. 
 
 ## Background
diff --git a/credhub.html.md.erb b/credhub.html.md.erb
@@ -3,6 +3,8 @@ title: CredHub
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 BOSH CredHub is a secure credential management component that runs on the BOSH VM to minimize the surface area where credentials can be compromised.
 This topic provides resources for configuring service tiles to store their internal credentials in BOSH CredHub, instead of encoding them in product template and job template files.
 
diff --git a/development.html.md.erb b/development.html.md.erb
@@ -3,6 +3,8 @@ title: Development Steps at Each Level
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic describes the typical steps that tile developers follow when developing a tile at a given [integration level](./stages.html),
 such as brokered service tile, a managed service tile, or an on-demand service tile.
 
diff --git a/embedded-agents.html.md.erb b/embedded-agents.html.md.erb
@@ -3,6 +3,8 @@ title: Embedded Agents
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic provides resources for configuring services that use software agents embedded in application containers.
 
 ## <a id="overview"></a> Overview
diff --git a/environments.html.md.erb b/environments.html.md.erb
@@ -3,9 +3,11 @@ title: Development Environments
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to set up tile development environments, from simple standalone tools to a full PCF development environment. As you progress through the [stages](./stages.html) of tile development, you will likely also progress through these environments.
 
-## <a id="pcfdev"></a> PCF Dev and BOSH Lite
+## <a id="pcfdev"></a> PCF Dev and BOSH-Lite
 
 Pivotal provides a lightweight (vagrant packaged) instance of PCF with some
 basic services as a free product named PCF Dev. This is a great environment
diff --git a/get-credhub-vars.html.md.erb b/get-credhub-vars.html.md.erb
@@ -3,6 +3,8 @@ title: Fetching Variable Names and Values
 owner: CredHub
 ---
 
+<strong><%= modified_date %></strong>
+
 ## Overview
 
 CredHub has two API endpoints to identify and re-use variables. Operators who want to see all the credentials associated with their product, or support engineers who want to troubleshoot issues specific to one virtual machine (VM), can use these APIs for those purposes.
diff --git a/index.html.md.erb b/index.html.md.erb
@@ -3,6 +3,8 @@ title: PCF Tile Developer Guide
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 ## <a id="why"></a> Why Tiles?
 
 Whether you are an Independent Software Vendor (ISV) or an internal Pivotal service team, integrating your software service with Pivotal Cloud Foundry (PCF) makes the service easily available and usable by the growing PCF ecosystem. Pivotal supports these integrations and is committed to making the process as easy as possible.
diff --git a/managed.html.md.erb b/managed.html.md.erb
@@ -3,6 +3,8 @@ title: Managed Service
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 The topics in this subsection explain how to integrate your [brokered service](./brokered.html) more closely with Pivotal Cloud Foundry (PCF) to create a managed service and service tile for PCF.
 
 ## <a id="overview"></a> Overview
diff --git a/migrating-credhub-credentials.html.md.erb b/migrating-credhub-credentials.html.md.erb
@@ -3,6 +3,8 @@ title: Migrating Existing Credentials to CredHub
 owner: CredHub
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to migrate non-configurable secrets from Ops Manager into CredHub.
 
 ## <a id="cred-types"></a>CredHub Credential Types
diff --git a/nozzle.html.md.erb b/nozzle.html.md.erb
@@ -3,6 +3,8 @@ title: Logs, Metrics, and Nozzles
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to integrate PCF services with Cloud Foundry's logging system, the _Loggregator_, by writing to and reading from its _Firehose_ endpoint.
 
 ## <a id="overview"></a> Overview
diff --git a/odb-resource-defaults.html.md.erb b/odb-resource-defaults.html.md.erb
@@ -3,6 +3,8 @@ title: Configuring Disk and VM Type Defaults for On-Demand Service Tiles
 owner: Ops Manager
 ---
 
+<strong><%= modified_date %></strong>
+
 <p class="note"><strong>Note</strong>: Ops Manager 2.0 and later supports defining VM and disk type defaults and constraints.</p>
 
 This topic describes how tile authors can configure the dropdown menu items for VM types and persistent disk types in their tile.
diff --git a/on-demand.html.md.erb b/on-demand.html.md.erb
@@ -3,6 +3,8 @@ title: On-Demand Service
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to integrate your software as an on-demand service and service tile for PCF.
 
 ## <a id="overview"></a> Overview
diff --git a/other-integrations.html.md.erb b/other-integrations.html.md.erb
@@ -3,6 +3,7 @@ title: Other Integrations
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
 
 ## <a id="overview"></a> Overview
 
diff --git a/overview.html.md.erb b/overview.html.md.erb
@@ -3,6 +3,8 @@ title: Service Integration Overview
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 As a new tile developer, your process typically starts with learning about Pivotal Cloud Foundry (PCF) buildpacks, service brokers, tiles, and other components. Then you scope your development effort, set up your development tools and validation suite, and iterate development through increasing [levels of integration](#levels).
 
 The staged approach enables early feedback on the value and the design of the integration. This feedback helps you decide what level of integration to target in the future.
diff --git a/pcf-command.html.md.erb b/pcf-command.html.md.erb
@@ -3,6 +3,8 @@ title: pcf Command Line Utility
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 The `pcf` utility provides a command line interface to Pivotal Cloud Foundry for
 the purpose of deploying and testing tiles. Its primary reason for existence is
 to enable Ops Manager access from CI pipelines, but developers also find it
diff --git a/product-template-reference.html.md.erb b/product-template-reference.html.md.erb
@@ -3,6 +3,8 @@ title: Product Template Reference
 owner: Ops Manager
 ---
 
+<strong><%= modified_date %></strong>
+
 This document defines the separate pieces of a product template.
 For the purpose of explanation we use the [PCF example tile](https://github.com/pivotal-cf-experimental/ops-manager-example),
 a functional tile provided by the Ops Manager engineering team that deploys the NGINX web server.
diff --git a/property-reference.html.md.erb b/property-reference.html.md.erb
@@ -3,6 +3,8 @@ title: Property Reference
 owner: Ops Manager
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how PCF Tiles describe properties.
 
 ## <a id='expressions'></a>Double-Parentheses Expressions
diff --git a/publish.html.md.erb b/publish.html.md.erb
@@ -3,6 +3,8 @@ title: Publish and Update
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic provides resources to help you publish and update your service tile for Pivotal Cloud Foundry (PCF).
 
 ## <a id="publish"></a> Publish Your Tile
diff --git a/reference.html.md.erb b/reference.html.md.erb
@@ -3,6 +3,8 @@ title: References
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic collects API, configuration property, and other references for building Pivotal Cloud Foundry (PCF) tiles.
 
 ## <a id="troubleshooting"></a>Troubleshooting
diff --git a/release-notes-2-3.html.md.erb b/release-notes-2-3.html.md.erb
@@ -3,8 +3,9 @@ title: PCF v2.3 Partners Release Notice
 owner: Technical Program Management
 ---
 
-This topic describes the changes that Pivotal Cloud Foundry (PCF) v2.3 introduces which may be relevant to partner service tiles.
+<strong><%= modified_date %></strong>
 
+This topic describes the changes that Pivotal Cloud Foundry (PCF) v2.3 introduces which may be relevant to partner service tiles.
 
 ## <a id="om-credhub"></a> Ops Manager Credentials Stored in CredHub
 
diff --git a/release-notes.html.md.erb b/release-notes.html.md.erb
@@ -3,8 +3,9 @@ title: PCF v2.3 Partners Release Notice
 owner: Technical Program Management
 ---
 
-This topic describes the changes that Pivotal Cloud Foundry (PCF) v2.3 introduces which may be relevant to partner service tiles.
+<strong><%= modified_date %></strong>
 
+This topic describes the changes that Pivotal Cloud Foundry (PCF) v2.3 introduces which may be relevant to partner service tiles.
 
 ## <a id="om-credhub"></a> Ops Manager Credentials Stored in CredHub
 
diff --git a/releases.html.md.erb b/releases.html.md.erb
@@ -3,6 +3,8 @@ title: Partner Software Product Release Cycle
 owner: London Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic describes the four phases of product release to Pivotal Cloud Foundry (PCF).
 
 ## <a id='alpha'></a>Phase 1: Alpha
diff --git a/roadmap.html.md.erb b/roadmap.html.md.erb
@@ -3,6 +3,8 @@ title: Service Development Roadmap
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 Pivotal recommends that developers create service tiles iteratively, starting at the lowest level of
 integration and successively re-developing their code for increasing [levels of integration](./stages.html).
 
diff --git a/runtime-config.html.md.erb b/runtime-config.html.md.erb
@@ -3,6 +3,8 @@ title: Managing Runtime Configs
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to define and manage named runtime configs with your service tile for Pivotal Cloud Foundry (PCF).
 
 Tile authors can [create a new runtime config](#create) in an existing product tile, [delete a runtime config](#delete) from a tile, or add a tile that contains a [runtime config only](#config-only).
diff --git a/sdk.html.md.erb b/sdk.html.md.erb
@@ -3,6 +3,8 @@ title: Pivotal Cloud Foundry Services SDK
 owner: London Services
 ---
 
+<strong><%= modified_date %></strong>
+
 ## Dynamic Provisioning, Metrics, and Backups
 
 The Pivotal Cloud Foundry (PCF) Services SDK is designed to help you build enterprise-ready service offerings for the Marketplace. 
diff --git a/service-brokers.html.md.erb b/service-brokers.html.md.erb
@@ -3,6 +3,8 @@ title: Service Brokers
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic provides resources for building service brokers and routing services.
 
 ## <a id="resources"></a> Service Broker Resources
diff --git a/ssi-creds-tiledev.html.md.erb b/ssi-creds-tiledev.html.md.erb
@@ -3,6 +3,8 @@ title: Securing Service Credentials with Runtime CredHub
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic describes how to develop your Pivotal Cloud Foundry (PCF) service tile to support secure service instance (SSI) credentials using [runtime CredHub](http://docs.pivotal.io/pivotalcf/2-0/credhub/#runtime).
 
 ## <a id="background"></a> Background
diff --git a/stages.html.md.erb b/stages.html.md.erb
@@ -3,6 +3,8 @@ title: Levels of Integration
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 ## <a id="levels"></a> Integration Levels
 
 A service can integrate with PCF at four levels, shown here in order of increasing integration. In general, user-experience and production-readiness improves as the integration level increases. But none of the higher levels is required. You can stop service integration and declare it complete (enough) after any of these:
diff --git a/tile-basics.html.md.erb b/tile-basics.html.md.erb
@@ -3,6 +3,8 @@ title: Tile Basics
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This section gives a high-level overview of how tiles, Pivotal Cloud Foundry (PCF), and PCF service brokers work together.
 
 ## <a id="cf-broker"></a>Cloud Foundry Service Brokers and PCF Tiles
diff --git a/tile-documentation.html.md.erb b/tile-documentation.html.md.erb
@@ -3,6 +3,8 @@ title: Tile Documentation
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic explains how to document your service tile for Pivotal Cloud Foundry (PCF).
 
 ## <a id="overview"></a> Overview
diff --git a/tile-errands.html.md.erb b/tile-errands.html.md.erb
@@ -3,6 +3,8 @@ title: Errands
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 Lifecycle errands are BOSH errands (scripts) that run at the beginning and end of an installed product's availability time. Product teams create errands as part of a product package, and a product can only run errands it includes.
 
 For more information about BOSH errands, see [BOSH documentation](https://bosh.io/docs/errands), and for more information about errands in Pivotal Cloud Foundry (PCF), see [Managing Errands in Ops Manager](http://docs.pivotal.io/pivotalcf/1-10/customizing/managing_errands.html).
diff --git a/tile-generator.html.md.erb b/tile-generator.html.md.erb
@@ -3,8 +3,9 @@ title: Tile Generator
 owner: Services
 ---
 
-This topic describes the Tile Generator tool, which helps tile authors develop, package, test, and deploy services and other add-ons to Pivotal Cloud Foundry (PCF).
+<strong><%= modified_date %></strong>
 
+This topic describes the Tile Generator tool, which helps tile authors develop, package, test, and deploy services and other add-ons to Pivotal Cloud Foundry (PCF).
 
 ## <a id="overview"></a> Overview
 
diff --git a/tile-structure.html.md.erb b/tile-structure.html.md.erb
@@ -3,6 +3,8 @@ title: How Tiles Work
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 Product tiles make it easy for cloud operators to offer new and upgraded software services to developers in a Pivotal Cloud Foundry (PCF) deployment. [Pivotal Network](https://network.pivotal.io) distributes these tiles as zipped code directories, with filename extension `.pivotal`, that contain or point to all of the software elements that perform the tile's functions.
 
 This topic explains what each functional element of a tile does and how you create or specify it as input to the [Tile Generator](./tile-generator.html) tool that creates `.pivotal` files.
diff --git a/tile-upgrades.html.md.erb b/tile-upgrades.html.md.erb
@@ -3,6 +3,8 @@ title: Tile Upgrades
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 This topic discusses product tile migrations, which refers to changing the name and values of properties when a customer upgrades tile versions. Tile authors supply a JavaScript file to trigger chaining migrations. Chaining migrations allows for multiple migrations to run sequentially.   
 
 <p class="note"><strong>Note</strong>: In order to use JS migrations, ensure you are using Ops Manager 1.7 or later.</p>
diff --git a/tools.html.md.erb b/tools.html.md.erb
@@ -3,6 +3,8 @@ title: Development Tools
 owner: Services
 ---
 
+<strong><%= modified_date %></strong>
+
 The topics in this section describe tools that Pivotal uses and recommends for tile development.
 
 * [Tile Generator](./tile-generator.html) takes a service software, a service broker, optional other components, and a simple configuration file and creates a tile and everything else required to deploy your software into PCF.
diff --git a/workflow.html.md.erb b/workflow.html.md.erb
@@ -3,8 +3,9 @@ title: Tile Development Workflow
 owner: Services
 ---
 
-The topics in this section explain the high-level sequence of steps that Pivotal recommends for developing a service tile.
+<strong><%= modified_date %></strong>
 
+The topics in this section explain the high-level sequence of steps that Pivotal recommends for developing a service tile.
 
 * [Services Integration Overview](./overview.html) diagrams and explains the staged service integration process at the highest level, from learning how tiles work and deciding on the scope of an integration effort to publishing, documenting, and maintaining your finished service tile.
 
