---
title: Ping Identity DevOps <code>pingcommon</code> Hook - <code>02-get-remote-server-profile.sh</code>
description: "This hook will get bits from a git repo based on SERVER_PROFILE_* variables passed to the container. If no SERVER_PROFILES are passed, then nothing will occur when running this hook. These bits will be placed into the STAGING_DIR location (defaults to ${BASE_DIR}/staging). Server Profiles may be layered to copy in profiles from a parent/ancestor server profile. An example might be a layer of profiles that look like: - Dev Environment Configs (DEV_CONFIG) - Dev Certificates (DEV_CERT) - Base Configs (BASE) This would result in a set of SERVER_PROFILE variables that looks like: - SERVER_PROFILE_URL=...git url of DEV_CONFIG... - SERVER_PROFILE_PARENT=DEV_CERT - SERVER_PROFILE_DEV_CERT_URL=...git url of DEV_CERT... - SERVER_PROFILE_DEV_CERT_PARENT=BASE - SERVER_PROFILE_BASE_URL=...git url of BASE... In this example, the bits for BASE would be pulled, followed by DEV_CERT, followed by DEV_CONFIG If other source maintenance repositories are used (i.e. bitbucket, s3, ...) then this hook could be overridden by a different hook"
component: devops
page_id: devops::docker-images/pingcommon/hooks/02-get-remote-server-profile.sh
canonical_url: https://developer.pingidentity.com/devops/docker-images/pingcommon/hooks/02-get-remote-server-profile.sh.html
section_ids:
  devops-ping-identity-devops-hook: Ping Identity DevOps pingcommon Hook - 02-get-remote-server-profile.sh
---

# Ping Identity DevOps `pingcommon` Hook - `02-get-remote-server-profile.sh`

## Ping Identity DevOps `pingcommon` Hook - `02-get-remote-server-profile.sh`

This hook will get bits from a git repo based on SERVER\_PROFILE\_\* variables passed to the container. If no SERVER\_PROFILES are passed, then nothing will occur when running this hook. These bits will be placed into the STAGING\_DIR location (defaults to ${BASE\_DIR}/staging). Server Profiles may be layered to copy in profiles from a parent/ancestor server profile. An example might be a layer of profiles that look like: - Dev Environment Configs (DEV\_CONFIG) - Dev Certificates (DEV\_CERT) - Base Configs (BASE) This would result in a set of SERVER\_PROFILE variables that looks like: - SERVER\_PROFILE\_URL=...git url of DEV\_CONFIG... - SERVER\_PROFILE\_PARENT=DEV\_CERT - SERVER\_PROFILE\_DEV\_CERT\_URL=...git url of DEV\_CERT... - SERVER\_PROFILE\_DEV\_CERT\_PARENT=BASE - SERVER\_PROFILE\_BASE\_URL=...git url of BASE... In this example, the bits for BASE would be pulled, followed by DEV\_CERT, followed by DEV\_CONFIG If other source maintenance repositories are used (i.e. bitbucket, s3, ...) then this hook could be overridden by a different hook

***

This document is auto-generated from *[pingcommon/opt/staging/hooks/02-get-remote-server-profile.sh](https://github.com/pingidentity/pingidentity-docker-builds/blob/master/pingcommon/opt/staging/hooks/02-get-remote-server-profile.sh)*

Copyright © 2026 Ping Identity Corporation