Removing components in a Deployment Template environment

This topic explains how the Deployment Template treats components that have been removed from its AppConfig.xml file. Incremental provisioning in the Deployment Template updates existing components, but does not remove components that are not defined in the AppConfig.xml.

In general, running initialize_services removes an application from both the EAC and the Endeca Workbench store, and re-provisions the application, so at that point you can be sure that the EAC has only the components provisioned in the Deployment Template.

When the Deployment Template performs its provisioning check, it verifies that all of the components currently listed in the AppConfig.xml are provisioned and up-to-date with the EAC copy of the components. Any new or modified components are provisioned or have their provisioning updated in the EAC at this time.

However, the Deployment Template does not consider components that are not declared in AppConfig.xml (including ones that were declared there at some point but since removed). This means that components that are provisioned in the EAC (including components previously provisioned with the Deployment Template) may remain—the Deployment Template supports an environment where it is not the only tool interacting with the EAC.

Example scenario

Following the provisioning step, whenever the Deployment Template runs a baseline update, it checks whether the definition in the AppConfig.xml file has changed compared to what is stored in the EAC Central Server. It picks up changes such as new flags or additional components.

However, if you modify the baseline update script by removing a Dgraph in the AppConfig.xml file, the baseline_update script honors the change, but does not affect the provisioning configuration stored in the EAC Central Server. It does issue a message about the discrepancy when running the script. The removed Dgraph continues running, even though it is no longer listed in the AppConfig.xml file.