Aug 9, 2023 · Aug 9, 2023 · Aug 9, 2023 · Aug 9, 2023
diff --git a/_docs/deployments/gitops/applications-dashboard.md b/_docs/deployments/gitops/applications-dashboard.md
diff --git a/_docs/deployments/gitops/create-application.md b/_docs/deployments/gitops/create-application.md

 ## Application: General configuration settings

 General configuration settings define the source, destination, and sync policies for the application.
 General configuration settings define thegroup to which the application belongs,source, destination, and sync policies for the application.

 {% include
   image.html
   max-width="70%"
   %}

 <!--- ### Groups
 Optional. The group or groups to which to add the application.
 You can group applications based on criteria meaningful to your organization, such as environment, region, or any other relevant attribute. You can then view deployments for these applications in the same location in the Groups tab of the GitOps Apps dashboard. A new view for GitOps Application, App Groups allow you to collate multiple applications view their timelines.

 Select an existing group, or create a new application group by typing a name and pressing Enter.

 -->

 ### Source
 The Git repository to be tracked for changes to the application's source code.
 {::nomarkdown}<ul> <li><b>Repository URL</b>: The Git repo or the Helm package repo with the application source code, to be tracked for changes. <br>If SSH is configured for the runtime, you can connect to the repo with either HTTPS or SSH. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul> {:/}
diff --git a/_docs/deployments/gitops/manage-application.md b/_docs/deployments/gitops/manage-application.md
  Optimize deployed applications by changing application definitions when needed.

 * [Synchronize applications](#manually-synchronize-an-application)
  Sync applications on-demand by manually applying sync options or selecting the resources to sync.
  Sync applications on-demand by manually applying sync options orby manuallyselecting the resources to sync.

 * [Rollback applications](#rollback-gitops-applications)
  Rollback an application to a previous deployment version.
 * [Terminate sync for applications](#terminate-on-going-sync-for-gitops-applications)
  With a single-click, terminate on-going sync processes when needed.

 * [Refresh applications](#refreshhard-refresh-gitops-applications)
  Manually refresh applications with a single-click, as an alternative to manually synchronizing them.

 * [Rollback applications](#rollback-gitops-applications)
  Rollback applications to previous deployment versions.

 * [Manage rollouts for deployments](#manage-rollouts-for-deployments)
 * [Manage rollouts for deployments](#manage-rollouts-for-gitops-application-deployments)
  Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

 * [Delete applications](#delete-an-application)
 * [Delete applications](#delete-gitops-applications)
  Delete unused or legacy applications to avoid clutter and remove unnecessary resources.

  To delete specific resources within an application, see [Delete application resources]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/#delete-application-resources).








 ## Manually synchronize an application
 Manually synchronize an application to expedite Git-to-cluster sync.  The sync options selected for manual sync override the sync options defined for the application.
 The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application.

 >You can also synchronize application resources with sync statuses,  such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. The context menu of the resource shows the Sync option.
 >**TIP**:
 You can also synchronize _application resources_ with sync statuses such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. Select the Sync option from resource's context menu.

 **Before you begin**
 * Review:
 <br><br>
 {:/}


 ## Terminate on-going sync for GitOps applications
 Manually terminate an on-going synchronization process for the application. You may need to terminate an on-going sync that remains indefinitely as Syncing, or because you have detected problems in the current deployment
 Terminating a sync operation reverts the deployment to the previously deployed version or image.

 1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
 1. If needed, filter by **Status** **Syncing** to view applications with active sync operations.
 1. Select the application and then from the application header, click **Terminate Sync**.

   {% include
   image.html
   lightbox="true"
   file="/images/applications/app-terminate-sync.png"
   url="/images/applications/app-terminate-sync.png"
   alt="Manually terminate on-going sync"
   caption="Manually terminate on-going sync"
   max-width="50%"
   %}


 ## Refresh/hard refresh GitOps applications

 As an alternative to manually syncing an application, either refresh or hard refresh the application. Both options are always available in the application toolbar.

 1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
 1. Select the application, and then from the top-right, select the required action:
  * **Refresh**: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.
  * **Hard Refresh**: Refresh the application to sync with the Git state, while removing the cache.

   {% include
   image.html
   lightbox="true"
   file="/images/applications/app-refresh-hard-refresh.png"
   url="/images/applications/app-refresh-hard-refresh.png"
   alt="Refresh/Hard Refresh for applications"
   caption="Refresh/Hard Refresh for applications"
   max-width="50%"
   %}

 ## Rollback GitOps applications
 Rollback to a previously deployed version of active GitOps applications. You may want to rollback a newly deployed version due to errors in your code or misconfigurations, etc.

 max-width="70%"
 %}

 ## Manage rollouts for deployments
 ## Manage rollouts forGitOps applicationdeployments
 Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

 {::nomarkdown}
 |**Retry**              | Retry a rollout that has been aborted. Available only when a rollout has been aborted. |
 |**Skip-current-step**  | Skip executing the current step, and continue with the next step. |

 ## Deletean application
 ## DeleteGitOps applications
 Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the GitOps Apps dashboard in Codefresh.

 >**Prune resources** in the application's General settings determines the scope of the delete action.
diff --git a/images/applications/app-refresh-hard-refresh.png b/images/applications/app-refresh-hard-refresh.png
diff --git a/images/applications/app-terminate-sync.png b/images/applications/app-terminate-sync.png
diff --git a/images/applications/current-state-delete-resource.png b/images/applications/current-state-delete-resource.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -38,7 +38,7 @@ Application definitions include the name, runtime, and the name of the YAML mani

		## Application: General configuration settings

		General configuration settings define the source, destination, and sync policies for the application.
		General configuration settings define thegroup to which the application belongs,source, destination, and sync policies for the application.

		{% include
		image.html
Expand All		@@ -50,6 +50,14 @@ General configuration settings define the source, destination, and sync policies
		max-width="70%"
		%}

		<!--- ### Groups
		Optional. The group or groups to which to add the application.
		You can group applications based on criteria meaningful to your organization, such as environment, region, or any other relevant attribute. You can then view deployments for these applications in the same location in the Groups tab of the GitOps Apps dashboard. A new view for GitOps Application, App Groups allow you to collate multiple applications view their timelines.

		Select an existing group, or create a new application group by typing a name and pressing Enter.

		-->

		### Source
		The Git repository to be tracked for changes to the application's source code.
		{::nomarkdown}<ul> <li><b>Repository URL</b>: The Git repo or the Helm package repo with the application source code, to be tracked for changes. <br>If SSH is configured for the runtime, you can connect to the repo with either HTTPS or SSH. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul> {:/}
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,18 +12,25 @@ Application creation and deployment is one part of the continuous deployment/del
		Optimize deployed applications by changing application definitions when needed.

		* [Synchronize applications](#manually-synchronize-an-application)
		Sync applications on-demand by manually applying sync options or selecting the resources to sync.
		Sync applications on-demand by manually applying sync options orby manuallyselecting the resources to sync.

		* [Rollback applications](#rollback-gitops-applications)
		Rollback an application to a previous deployment version.
		* [Terminate sync for applications](#terminate-on-going-sync-for-gitops-applications)
		With a single-click, terminate on-going sync processes when needed.

		* [Refresh applications](#refreshhard-refresh-gitops-applications)
		Manually refresh applications with a single-click, as an alternative to manually synchronizing them.

		* [Rollback applications](#rollback-gitops-applications)
		Rollback applications to previous deployment versions.

		* [Manage rollouts for deployments](#manage-rollouts-for-deployments)
		* [Manage rollouts for deployments](#manage-rollouts-for-gitops-application-deployments)
		Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

		* [Delete applications](#delete-an-application)
		* [Delete applications](#delete-gitops-applications)
		Delete unused or legacy applications to avoid clutter and remove unnecessary resources.

		To delete specific resources within an application, see [Delete application resources]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/#delete-application-resources).




Expand DownExpand Up		@@ -95,11 +102,13 @@ Update General or Advanced configuration settings for a deployed application thr




		## Manually synchronize an application
		Manually synchronize an application to expedite Git-to-cluster sync. The sync options selected for manual sync override the sync options defined for the application.
		The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application.

		>You can also synchronize application resources with sync statuses, such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. The context menu of the resource shows the Sync option.
		>TIP:
		You can also synchronize _application resources_ with sync statuses such as `Service`, `AnalysisTemplate`, and `Rollouts` resources for example, in the Current State tab. Select the Sync option from resource's context menu.

		Before you begin
		* Review:
Expand DownExpand Up		@@ -222,6 +231,45 @@ For example, if you made changes to `api` resources or `audit` resources, type `
		<br><br>
		{:/}


		## Terminate on-going sync for GitOps applications
		Manually terminate an on-going synchronization process for the application. You may need to terminate an on-going sync that remains indefinitely as Syncing, or because you have detected problems in the current deployment
		Terminating a sync operation reverts the deployment to the previously deployed version or image.

		1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
		1. If needed, filter by Status Syncing to view applications with active sync operations.
		1. Select the application and then from the application header, click Terminate Sync.

		{% include
		image.html
		lightbox="true"
		file="/images/applications/app-terminate-sync.png"
		url="/images/applications/app-terminate-sync.png"
		alt="Manually terminate on-going sync"
		caption="Manually terminate on-going sync"
		max-width="50%"
		%}


		## Refresh/hard refresh GitOps applications

		As an alternative to manually syncing an application, either refresh or hard refresh the application. Both options are always available in the application toolbar.

		1. In the Codefresh UI, from Ops in the sidebar, select [GitOps Apps](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
		1. Select the application, and then from the top-right, select the required action:
		* Refresh: Retrieve desired (Git) state, compare with the live (cluster) state, and refresh the application to sync with the desired state.
		* Hard Refresh: Refresh the application to sync with the Git state, while removing the cache.

		{% include
		image.html
		lightbox="true"
		file="/images/applications/app-refresh-hard-refresh.png"
		url="/images/applications/app-refresh-hard-refresh.png"
		alt="Refresh/Hard Refresh for applications"
		caption="Refresh/Hard Refresh for applications"
		max-width="50%"
		%}

		## Rollback GitOps applications
		Rollback to a previously deployed version of active GitOps applications. You may want to rollback a newly deployed version due to errors in your code or misconfigurations, etc.

Expand DownExpand Up		@@ -316,7 +364,7 @@ caption="Rollback completed for application"
		max-width="70%"
		%}

		## Manage rollouts for deployments
		## Manage rollouts forGitOps applicationdeployments
		Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.

		{::nomarkdown}
Expand DownExpand Up		@@ -426,7 +474,7 @@ The table describes the options for the `Rollout` resource.
		\|Retry \| Retry a rollout that has been aborted. Available only when a rollout has been aborted. \|
		\|Skip-current-step \| Skip executing the current step, and continue with the next step. \|

		## Deletean application
		## DeleteGitOps applications
		Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the GitOps Apps dashboard in Codefresh.

		>Prune resources in the application's General settings determines the scope of the delete action.
Expand Down