Configuration Drift Correction in Deploy
A configuration drift can occur when changes are made to the infrastructure of a target system outside of the defined deployment environment. This results in state of the deployment system being out of sync with the actual state of the target system.
Deploy can detect state changes in the infrastructure of the target system and repair the configuration drift using the desired state defined in Deploy.
Configuration drift detection model
Deploy has a built-in mechanism that allows you to discover the infrastructure and configuration of middleware running on a target platform. For example, in WebSphere, Deploy can discover all the clusters, nodes, servers, datasources, or queues. For cloud platforms like Azure, Deploy can discover resource groups, app services, virtual machines, and others.
The discovery mechanism in Deploy is extensible through plugins allowing you to adapt to various discovery scenarios. For more information on how the discovery mechanism works, refer to Discover middleware.
Repairing system states using configuration drift
The Deploy model based deployment engine can generate deployment steps required to apply configuration changes to a target system.
Target environments, environment configuration settings (dictionaries), application components, application configuration, and application middleware configuration are modeled in a declarative manner in Deploy using the Unified Deployment Model (UDM).
For more information on how the Deploy deployment model works, refer to:
When configuration drift is detected, Deploy uses the deployment engine to redeploy the desired state to the target system.
To see how you can create a job schedule for detecting configuration drifts, refer to Define a job schedule.
To view and correct a configuration drift, refer to View and correct a detected drift.