From b8d592dd541ff373b54e861fd8cf21592667f1b8 Mon Sep 17 00:00:00 2001
From: Brian Angelica <91690569+bangelic@users.noreply.github.com>
Date: Fri, 19 Jul 2024 12:14:27 -0400
Subject: [PATCH] Add Hammer CLI procedure for corrupted content (#3137)

A CLI procedure was needed for repairing corrupted
content on a SmartProxy. There are 3 optional parameters for
repairing corrupted content as well as a global fix.
---
 guides/common/assembly_importing-content.adoc |  2 +
 ...ng-corrupted-content-on-a-smart-proxy.adoc | 40 +++++++++++++++++++
 2 files changed, 42 insertions(+)
 create mode 100644 guides/common/modules/proc_recovering-corrupted-content-on-a-smart-proxy.adoc

diff --git a/guides/common/assembly_importing-content.adoc b/guides/common/assembly_importing-content.adoc
index d6f63144937..3167e3d555d 100644
--- a/guides/common/assembly_importing-content.adoc
+++ b/guides/common/assembly_importing-content.adoc
@@ -182,6 +182,8 @@ include::modules/proc_configuring-selinux-to-permit-content-synchronization-on-c
 
 include::modules/proc_recovering-a-corrupted-repository.adoc[leveloffset=+1]
 
+include::modules/proc_recovering-corrupted-content-on-a-smart-proxy.adoc[leveloffset=+1]
+
 include::modules/proc_republishing-repository-metadata.adoc[leveloffset=+1]
 
 include::modules/proc_republishing-content-view-metadata.adoc[leveloffset=+1]
diff --git a/guides/common/modules/proc_recovering-corrupted-content-on-a-smart-proxy.adoc b/guides/common/modules/proc_recovering-corrupted-content-on-a-smart-proxy.adoc
new file mode 100644
index 00000000000..0108fda3ad2
--- /dev/null
+++ b/guides/common/modules/proc_recovering-corrupted-content-on-a-smart-proxy.adoc
@@ -0,0 +1,40 @@
+[id="Recovering_Corrupted_Content_on_{smart-proxy-context}_{context}"]
+= Recovering corrupted content on {SmartProxy}
+
+If the client is unable to consume content from a published repository to which it has a subscription, the content has been corrupted and needs to be repaired.
+In case of content corruption on a {SmartProxy}, you can recover it by using the `verify-checksum` command in Hammer CLI.
+The `verify-checksum` command can repair content in a content view, lifecycle environment, repository, or all content on {SmartProxy}.
+You can track the progress of a command by navigating to *Monitor* > *{Project} Tasks* > *Tasks* and searching for the action *Verify checksum for content on smart proxy*.
+
+.CLI procedure
+* To repair content in a content view, run Hammer on your {SmartProxy}:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ {hammer-smart-proxy} content verify-checksum \
+--id __My_{smart-proxy-context-titlecase}_ID__ \
+--organization-id 1 --content-view-id 3
+----
+* To repair content in a lifecycle environment, run Hammer on your {SmartProxy}:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ {hammer-smart-proxy} content verify-checksum \
+--id __My_{smart-proxy-context-titlecase}_ID__ \
+--organization-id 1 --lifecycle-environment-id 1
+----
+* To repair content in a repository, run Hammer on your {SmartProxy}:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ {hammer-smart-proxy} content verify-checksum \
+--id __My_{smart-proxy-context-titlecase}_ID__ \
+--organization-id 1 --repository-id 1
+----
+* To repair all content on {SmartProxy}, run the following command:
++
+[options="nowrap", subs="+quotes,attributes"]
+----
+$ {hammer-smart-proxy} content verify-checksum \
+--id __My_{smart-proxy-context-titlecase}_ID__
+----