Updating and synchronizing stale configurations

Update and synchronize stale configurations in Cloudera Data Services on premises 1.5.5 SP3 and higher releases, when environmental settings, such as Proxy or LDAP in the Cloudera Management Console, or Kerberos in Cloudera Base on premises, change.

Cloudera Data Engineering UI
Cloudera Data Engineering API

In the Cloudera console, click the Data Engineering tile. The Cloudera Data Engineering Home page is displayed.
Click Administration in the left navigation menu. The Administration page is displayed.
In the Services column, select the service for which you want to synchronize the stale configurations.
important
If any configurations are updated in the Cloudera Management Console or Cloudera Base on premises after creating the Service, a banner is automatically displayed with the Review & Sync button under the Service name or at the top of the Service Details page.
Figure 1. Stale configuration detected message
Click the Review & Sync button. The Confirm Service Synchronization modal window opens.
The Confirm Service Synchronization modal window displays the configuration changes and the service pods to restart.
Figure 2. Confirm Service Synchronization modal window
Verify the changes and click the Restart and Sync button.
- If all the configurations are correctly applied and synchronized, the Cloudera Data Engineering Service restarts successfully.
- If the synchronization fails, retry the synchronization process again.

You must use the ServiceAdmin role and verify if the Cloudera Data Engineering Service is up to date with the Cloudera Data Services on premises configurations.
```
cdpcurl -X GET '[***CDP_ENDPOINT***]/dex/api/v1/cluster/[***CLUSTER-ID***]/config-status' \
     --access_key <ACCESS-KEY> \
    --private_key <PRIVATE-KEY>
```
important
- To generate an API access key, see Generating an API access key.
- For more information about the cdpcurl command, see cdpcurl page.
- Use -k in the command only if your Cloudera Data Services on premises certificate is not trusted on your machine.

Run the following API to apply the changes to the Cloudera Data Engineering Service and restart the Service:

cdpcurl -X POST '[***CDP_ENDPOINT***]/dex/api/v1/cluster/[***CLUSTER-ID***]/config-restart' \
     --access_key <ACCESS-KEY> \
    --private_key <PRIVATE-KEY>