> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/3.0/harness-platform-resources/secrets/secrets-management/reconcilation-of-secret-manager-template.md).

# Reconciliation of Secret Manager Template

Secret Manager Template reconciliation is the process of updating dependent Custom Secret Managers and Secrets when you modify their associated template. When you update a Secret Manager Template, all entities that use it need to be updated to match the new template settings.

**How it works:**

* Harness automatically detects when a template has been modified
* Alert banners appear on all dependent entities (Custom Secret Managers and Secrets)
* You can review the configuration differences in a YAML diff view
* Apply the changes to keep all the entities synchronized

This article guides you through the reconciliation process for both Custom Secret Managers and their dependent Secrets.

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

Before you can reconcile templates, ensure you have the following configured:

* A [Secret Manager Template](/harness-ai/use-harness-platform/templates/create-a-secret-manager-template.md)
* A [Custom Secret Manager](/harness-ai/use-harness-platform/secrets/secrets-management/custom-secret-manager.md) that references the Secret Manager Template
* A [Secret](/harness-ai/use-harness-platform/secrets/secrets-management/harness-secret-manager-overview.md) that uses the Custom Secret Manager

### Modify a Secret Manager Template <a href="#modify-a-secret-manager-template" id="modify-a-secret-manager-template"></a>

To show how reconciliation works, let's update a Secret Manager Template. In this example, we'll change template values from fixed values to runtime inputs:

1. Navigate to your Secret Manager Template in the Templates section
2. Click the **More options** (⋮) menu and select **Open/Edit Template**
3. In the **Configuration** section, change any value from **Fixed value** to **Runtime Input**
4. Click **Save** to apply your template updates

{% hint style="info" %}
**WHAT HAPPENS NEXT?**

After saving the template changes, Harness automatically identifies all dependent Custom Secret Managers and Secrets that need to be updated. Reconciliation alerts will appear on these entities to guide you through the update process.
{% endhint %}

### Reconcile the Secret Manager <a href="#reconcile-the-secret-manager" id="reconcile-the-secret-manager"></a>

After updating the template, you need to reconcile each Custom Secret Manager that references it

* Navigate to the Custom Secret Manager and click **Reconcile** in the alert banner
* On the details page, click **Reconcile** again to view the YAML diff
* Review the configuration changes, provide values for any runtime inputs, and click **Continue** to apply

### Reconcile the Secret <a href="#reconcile-the-secret" id="reconcile-the-secret"></a>

After reconciling the Secret Manager, update all dependent secrets:

* Navigate to each Secret that uses the Custom Secret Manager and click **Reconcile** in the alert banner
* On the Secret editing page, click **Reconcile** again to view the YAML diff
* Review the configuration changes, provide values for any runtime inputs, and click **Save** to apply

{% hint style="info" %}
**IMPORTANT NOTE**

If a Secret is created in a Custom Secret Manager that needs reconciliation, Harness will redirect you to the [Secret Manager page](#reconcile-the-secret-manager) to complete the Custom Secret Manager reconciliation first.

<details>

<summary>Click to view</summary>

![](/files/UvnVjll8t2IJqLb2VGsa)

</details>
{% endhint %}