Review Deployment
In the following scenarios, a comparison page highlighting discrepancies between the tenant’s current configurations and the applied baseline will be generated, and the status of the tenant will display Review deployment.
- When a baseline is applied to a tenant and Elements completes the configuration comparison process.
- When the baseline of a tenant is changed, triggering a new configuration comparison process, and the process is complete.
For a tenant with this status, you need to review configurations, make updates as needed, and initiate the deployment process to deploy the finalized configurations to the tenant.
To open the comparisons page, on the Tenants page, locate the tenant, and click the Review deployment status link.
In the summary section, you can find the following information:
- Tenant name and customer’s organization name
- Baseline name, baseline version, and baseline color
If multiple baselines are applied to the tenant, they will be listed in the ranking order for clarity.
- Last deployed time and the **View change log** link
The **View change log** link allows you to track tenant modifications over time. For detailed instructions, refer to [View Change Logs](#missing-link).
In the comparisons section, configuration comparisons are grouped into 4 tabs. For quick access, you can search for a specific configuration by entering the configuration name in the **Search** text box and pressing **Enter** on your keyboard. If you want to focus on configurations from a specific baseline, click **Filter**, select the desired baseline, and click **Apply changes**.
Switch among these 4 tabs to review and manage the configurations. Note that only the selected configurations will be deployed to the tenant.
- **Conflicts with baseline** – This tab displays the configurations that are configured differently (same instance name and mismatched property values) in the tenant and the baseline. You can expand or collapse all configurations under this tab by clicking **Expand all** or **Collapse all**.
To view and manage the conflicts of an instance, you can click **Edit** next to the instance. The **Edit** window pops up, displaying properties in pairs (tenant vs. baseline), which allows you to update and confirm the settings to be deployed. Select the standard for each pair, and click **Update** to save the changes.
If a property cannot be updated, a **View only** tag will appear next to it. To help streamline the review process, you can click **Hide view-only** **properties** to focus only on those modifiable properties.
For easier review, matching properties are hidden by default, helping you focus on conflicts. You can click **Show matching properties** if you want to display these matching properties, and you can make updates to these matching configurations, if needed.
Mark an instance as tenant-specific setting – If you want to mark an instance as tenant-specific setting, click **Mark as tenant-specific setting** next to the instance. Enter a comment and click **Save**. A **Tenant-specific setting** tag will appear next to it. Once an instance is marked as tenant-specific setting, it will still be included in the configuration deployment. However, drift detection will now use this custom value as the new standard for detecting deviations. To unmark an instance as tenant-specific setting, click **Unmark**, enter a comment, and click **Save** to save the changes. The **Tenant-specific setting** tag will disappear. Once an instance is unmarked as tenant-specific setting, it will still be monitored based on the baseline standard in drift detection.
Mark properties of an instance as tenant-specific settings – If you want to mark properties of an instance as tenant-specific settings, click **Edit** next to the instance to open the **Edit** window. In the **Edit** window, select the properties, and click **Mark as tenant-specific setting**. A **Tenant-specific setting** tag will appear next to the properties. Once a property is marked as tenant-specific setting, it will still be included in the configuration deployment. However, drift detection will now use this custom value as the new standard for detecting deviations. To unmark a property as tenant-specific setting, click **Unmark**, enter a comment, and click **Save** to save the changes. The **Tenant-specific setting** tag will disappear. Once a property is unmarked as tenant-specific setting, it will still be monitored based on the baseline standard in drift detection.
Accept deviation of an instance – If you want to accept a deviation of an instance, click **Accept deviation** next to the instance. Configure duration, enter a comment, and click **Save** to save the changes. An **Accepted instance** tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click **Cancel acceptance**. Enter a comment and click **Save** to save the changes. Canceling acceptance will re-enable drift detection for the instance.
Accept deviation of properties within an instance – If you want to accept deviation of properties within an instance, click **Edit** next to the instance to open the **Edit** window. In the **Edit** window, select the properties, and click **Accept deviation**. Configure duration, enter a comment, and click **Save** to save the changes. An **Accepted property** tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click **Cancel acceptance**. Enter a comment and click **Save** to save the changes. Canceling acceptance will re-enable drift detection for the properties.
- **Unique to** **baseline** – This tab displays the configurations that are exclusive to the baseline. You can expand or collapse all configurations under this tab by clicking **Expand all** or **Collapse all**.
You can make updates as below:
- Add all configurations – If you want to deploy all configurations to the tenant, click **Select all**.
- Add configurations within a source – If you want to deploy configurations within a source to the tenant, select the checkbox next to the source.
- Add a configuration – If you want to deploy a configuration to the tenant, expand the source to find the configuration, and select the checkbox next to the configuration.
- Add an instance – If you want to add an instance to the tenant, expand the source to find the configuration, expand the configuration to find the instance, and select the checkbox next to it.
- Update properties of an instance – If you want to update the properties of an instance, click **Edit** next to the instance to open the **Edit** window. In the **Edit** window, locate a property, make updates, and click **Update** to save the changes. If a specific property cannot be updated, a **View only** tag will appear next to it.
Accept deviation of an instance – If you want to accept a deviation of an instance, click Accept deviation next to the instance. Configure duration, enter a comment, and click Save to save the changes. An Accepted instance tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the instance.
- Accept deviation of properties within an instance – If you want to accept deviation of properties within an instance, click **Edit** next to the instance to open the **Edit** window. In the **Edit** window, select the properties, and click **Accept deviation**. Configure duration, enter a comment, and click **Save** to save the changes. An **Accepted property** tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click **Cancel acceptance**. Enter a comment and click **Save** to save the changes. Canceling acceptance will re-enable drift detection for the properties.
- **Unique to tenant** – This tab displays the configurations that are exclusive to the tenant. You can expand or collapse all configurations under this tab by clicking **Expand all** or **Collapse all**.
You can make updates as below:
- Remove all configurations – If you want to remove all configurations from the tenant, click **Deselect all**.
- Remove configurations within a source – If you want to remove configurations within a source from the tenant, deselect the checkbox next to the source.
- Remove a configuration – If you want to remove a configuration from the tenant, expand the source to find the configuration, and deselect the checkbox next to the configuration.
- Remove an instance – If you want to remove an instance from the tenant, expand the source to find the configuration, expand the configuration to find the instance, and deselect the checkbox next to the instance.
- Update properties of an instance – If you want to update the properties of an instance, click **Edit** next to the instance to open the **Edit** window. In the **Edit** window, locate a property, make updates, and click **Update** to save the changes.
If a property cannot be updated, a **View only** tag will appear next to it. To help streamline the review process, you can click **Hide view-only** **properties** to focus only on those modifiable properties.
Accept deviation of an instance – If you want to accept a deviation of an instance, click Accept deviationnext to the instance. Configure duration, enter a comment, and click Save to save the changes. An Accepted instance tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the instance.
Accept deviation of properties within an instance – If you want to accept deviation of properties within an instance, click Edit next to the instance to open the Edit window. In the Edit window, select the properties, and click Accept deviation. Configure duration, enter a comment, and click Save to save the changes. An Accepted property tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the properties.
- **Matches with baseline** – This tab displays the configurations that are configured identically (same instance name and property values) in the tenant and the baseline. You can expand or collapse all configurations under this tab by clicking **Expand all** or **Collapse all**.
To view details of an instance, click **View** next to the instance to open the **View** window. There is no need to make updates.
Once the current configurations meet your requirements, you can click Deploy in the lower-right corner of the page to initiate the deployment process to deploy the finalized configurations to the tenant. For detailed instructions, refer to Execute Deployment.
