Restoring Decision Intelligence Client Managed Software

When needed, restore the secrets and the PostgreSQL databases for Decision Intelligence Client Managed Software.

Procedure

Run the following command to make sure that you have the secrets <instance>-ads-designer-secret (if you installed Decision Designer), and <instance>-ads-runtime-secret (if you installed the decision runtime server).
```
kubectl get --namespace $ADS_RELEASE_NAMESPACE secrets
```
If you do not have the secrets, you can recreate them from the YAML file that you backed up:
```
oc create -f <my-ads-designer-secret.yaml>
```
And make sure that the encryptionKeys value corresponds to the time of the PostgreSQL backup to be restored.
If your deployment of Decision Intelligence uses external PostgreSQL databases, see the documentation of the PostgreSQL server provider for the restore procedure.

You must restore the entire database that is referenced in spec.decision_designer.database and spec.decision_runtime.database in the custom resources (CR).

If the PostgreSQL server where you restore the data is in a different instance from the server used for a backup, you might need to update the database parameters in the Decision Intelligence CR (spec.decision_designer.database and spec.decision_runtime.database) as well as the credentials and TLS certificates in secrets referenced from these sections (secret_name and ssl_secret_name).