---
title: Verifying Deployed Configuration
description: Continuous verification is an automated process to detect configuration drift by calling read (GET) APIs and validating responses against the current desired configuration to identify drift and possible paths to remediation. Ping Identity Solutions could have involvement with external systems or dynamic configuration. As such, the ongoing reverification of configuration should include testing to confirm against external configuration interference.
component: config-automation-promotion
page_id: config-automation-promotion:concepts:verifying_deployed_configuration
canonical_url: https://developer.pingidentity.com/config-automation-promotion/concepts/verifying_deployed_configuration.html
revdate: March 24, 2025
---

# Verifying Deployed Configuration

Continuous verification is an automated process to detect configuration drift by calling read (GET) APIs and validating responses against the current desired configuration to identify drift and possible paths to remediation. Ping Identity Solutions could have involvement with external systems or dynamic configuration. As such, the ongoing reverification of configuration should include testing to confirm against external configuration interference.

Forms of continuous verification include cron jobs running:

* Terraform plan (`terraform plan`) command returning empty plan. This might involve HCL that includes the Terraform `check {}` block that can provide warnings if non-managed configuration is seen to drift from defined assertions.

* Postman API collection of reads that include response verification tests.

* Node.js API test package.