Document PingData extension installation (#389)

BRASS-126

Author: henryrecker-pingidentity

docs/how-to/profilesPingDataExtensions.md

@@ -0,0 +1,25 @@
+---
+title: Including Extensions in PingData Server Profiles
+---
+# Including Extensions in PingData Server Profiles
+Server SDK extension zip files can be included in your server profile for PingData products (PingAuthorize, PingDataSync, PingDirectory, and PingDirectoryProxy). The zip files can be included directly, or can be pulled from a remote URL when the container starts up.
+
+# The pd.profile/server-sdk-extensions/ directory
+Any desired extension zip files should be included in the pd.profile/server-sdk-extensions/ directory of your server profile. Extension zip files in this directory will be installed during the setup process.
+
+# Pulling extension zip files from an external URL
+The hook scripts support pulling down extension zip files from a defined URL, to avoid having to commit zip archives to a Git repository. To do this, a `remote.list` file should be included in the extensions/ directory of your server profile. Any file with a name ending in `remote.list` in the extensions/ directory will be treated as a list of extensions.
+
+!!! note "Ensure extensions are in the right folder"
+When listing extensions to pull down via curl, the list must be placed in the extensions/ directory of the server profile. When directly including extension zip files, the zip files must be placed in the pd.profile/server-sdk-extensions/ directory of the server profile.
+
+For an example, see the extension list included in our [baseline PingDirectory server profile](https://github.com/pingidentity/pingidentity-server-profiles/blob/master/baseline/pingdirectory/extensions/baseline.remote.list).
+
+Separate multiple extensions with line breaks.
+
+A URL can also be specified in the downloaded zip file. To do this, add a space between the extension zip URL and the URL that will provide the SHA1 hash. For example:
+```
+https://example.com/extension.zip https://example.com/extension/sha1
+```
+
+Set the `ENABLE_INSECURE_REMOTE_EXTENSIONS` environment variable to `true` to allow installing extensions without the SHA1 hash check. By default the SHA1 check will be required. If a SHA1 URL is provided and the SHA does not match or the URL cannot be reached, the extension will not be installed.

docs/reference/profileStructures.md

@@ -106,6 +106,7 @@ Example at [getting-started/pingdirectory](https://github.com/pingidentity/pingi
 | pd.profile | Server profile matching the structure as defined by [PingDirectory Server Profiles](https://docs.pingidentity.com/bundle/pingdirectory-80/page/eae1564011467693.html)           |
 | instance   | Directories and files that you want to be used at product runtime, in accordance with the layout of the product. In general, this should be **non existing or empty**.          |
 | env-vars   | You can set environment variables used during deployment.  See [Variables and Scope](variableScoping.md) for more info.   In general, this should be **non existing or empty**. |
+| extensions   | You can provide URLs to download Server SDK extensions in a remote.list file.  See [Including Extensions in PingData Server Profiles](../how-to/profilesPingDataExtensions.md) for more info. |
 
 !!! note "Ping Data Server Profile Best Practices"
     * In most circumstances, the `pd.profile` directory should be the only directory in the server profile.

mkdocs.yml

@@ -127,6 +127,7 @@ nav:
               - PingDirectory Profile: "how-to/buildPingDirectoryProfile.md"
           - Layering: "how-to/profilesLayered.md"
           - ENV Substitution: "how-to/profilesSubstitution.md"
+          - Installing Extensions with PingData Profiles: "how-to/profilesPingDataExtensions.md"
           - Private Github Repos: "how-to/privateRepos.md"
       - Vault/Secrets: "how-to/usingVault.md"
       - Securing the Containers: "how-to/secureContainers.md"