links:

-title:Applications dashboard

localurl:/docs/deployment/applications-dashboard/

-title:Applications

-title:Creating applications

localurl:/docs/deployment/create-application/

-title:Managing applications

localurl:/docs/deployment/manage-application/

-title:Images in Codefresh

localurl:/docs/deployment/images/

-title:Install Argo Rollouts

pages:

-title:Applications dashboard

url:"/applications-dashboard"

-title:Applications

-title:Creating applications

url:"/create-application"

-title:Managing applications

url:"/manage-application"

-title:Images in Codefresh

url:"/images"

-title:Install Argo Rollouts

title:"Managing applications"

description:""

group:deployment

toc:true

Creating and deploying applications is the first part of the continuous deployment/delivery process. An equally important part is optimizing deployed applications when needed, including editing application definitions, and synchronizing or refreshing them on-demand.

* Edit applications

Optimize deployed applications by changing application definitions when needed.

* Synchronize applications

Sync applications on-demand by manually applying sync options or selecting which resources to sync.

Optimize deployed applications by updating General or Advanced configuration settings.

**How to**

1. In the Codefresh UI, go to the[Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="\_blank"}.

1. Do one of the following:

* Select the application to update, and then from the context menu on the right, select**Edit**.

* Click the application and then select the**Configuration** tab.

{% include

image.html

lightbox="true"

file="/images/applications/edit-app-configuration-tab.png"

url="/images/applications/edit-app-configuration-tab.png"

alt="Configuration tab with application settings"

caption="Configuration tab with application settings"

max-width="70%"

%}

{:start="3"}

1. Update the**General** or**Advanced** configuration settings as needed:

[General configuration]({{site.baseurl}}docs/deployment/create-application/#application-general-configuration-settings)

[Advanced configuration]({{site.baseurl}}docs/deployment/create-application/#advanced-configuration-settings)

When you change a setting, the Commit and Discard Changes buttons are displayed.

{% include

image.html

lightbox="true"

file="/images/applications/edit-app-change-setting.png"

url="/images/applications/edit-app-change-setting.png"

alt="Edit application settings"

caption="Edit application settings"

max-width="70%"

%}

{:start="4"}

1. Do one of the following:

* To_commit all changes_, click**Commit**. This final commit screen is displayed with a diff view of the changes.

* To_undo all changes_ and return to the previous settings, click**Discard Changes**. This action removes all the changes you have made so far and returns you to the Applications dashboard.

{% include

image.html

lightbox="true"

file="/images/applications/edit-app-diff-view.png"

url="/images/applications/edit-app-diff-view.png"

alt="Commit changes with diff view"

caption="Commit changes with diff view"

max-width="70%"

%}

{:start="5"}

1. To confirm all changes, at the bottom-left, click**Commit**.

The changes are committed to Git, and in a few moments also synced to the cluster.

{::nomarkdown}

<br><br>

{:/}

Synchonize applications manually to reconcile the desired state with the live state.

Instead of waiting for Argo CD to detect differences between the desired and live states and initate the sync if automated sync is enabled, expedite Git-to-cluster sync by selecting the relevant sync options or selecting the specific resources to sync.

On-demand application sync is useful if you have updated only a few resources.

Manual application sync options are grouped into:

* Revision settings with branch and Kubernetes apply options

* Additional settings with sync options as in the General application settings

* Synchonize Resource settings to selectively sync resources

For how-to instructions, see[Manually synchronize an application](#manually-synchronize-an-application).

{::nomarkdown}

<br>

{:/}

Revision settings determine the behavior for the branch you select.

**Revision**

The branch in Git to synchronize with the cluster.

**Prune**

When selected, removes legacy resources from the cluster that do not exist currently in the Git branch.

**Apply only**

When selected, uses the Kubernetes apply command (`kubectl apply`) to update the existing configuration with_only_ the changes.

For more information, see[In-place updates of resources](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#in-place-updates-of-resources), or read this[blog](https://www.containiq.com/post/kubectl-apply-vs-create).

**Dry run**

When selected, allows you to preview the application before changes are made to the cluster.

**Force**

When selected, orphans the dependents of a deleted resource during the sync operation. This option is useful to prevent accumulation of unused resources in deployed applications.

{::nomarkdown}

<br>

{:/}

{::nomarkdown}

<br>

{:/}

***Skip schema validation**

When selected, bypasses validating the YAML schema.

***Auto-create namespace**

When selected, automatically creates the namespace if the specified namespace does not exist in the cluster. If the namespace already exists, this setting is ignored.

***Prune last**

When selected, removes those resources that do not exist in the currently deployed version during the final wave of the sync operation. See[Prune last](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#prune-last){:target="\_blank"}.

***Apply out of sync only**

When selected, syncs only those resources in the application that have been changed and are`OutOfSync`, instead of syncing every resource regardless of their state. This option is useful to reduce load and save time when you have thousands of resources in an application. See <ahref="" >[Selective Sync](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#selective-sync){:target="\_blank"}.

***Respect ignore differences**

When selected, Argo CD omits resources defined for the`spec.ignoreDifferences` attribute from the sync. Otherwise, Argo CD implements the desired state ad-hoc during the sync operation. See[Respect ignore difference configs](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#respect-ignore-difference-configs){:target="\_blank"}.

{::nomarkdown}

<br>

{:/}

{::nomarkdown}Defines how resources are pruned, applying Kubernetes cascading deletion prune policies.

Read more at <ahref="https://kubernetes.io/docs/concepts/architecture/garbage-collection/#cascading-deletion"target="_blank">Kubernetes - Cascading deletion</a>.<ul><li><b>Foreground</b>: The default prune propagation policy used by Argo CD. With this policy, Kubernetes changes the state of the owner resource to`deletion in progress`, until the controller deletes the dependent resources and finally the owner resource itself. </li><li><b>Background</b>: When selected, Kubernetes deletes the owner resource immediately, and then deletes the dependent resources in the background.</li><li><b>Orphan</b>: When selected, Kubernetes deletes the dependent resources that remain orphaned after the owner resource is deleted.</li></ul> </br>{:/}

All Prune propagation policies can be used with:

**Replace**: When selected, Argo CD executes`kubectl replace` or`kubectl create`, instead of the default`kubectl apply` to enforce the changes in Git. This action will potentially recreate resources and should be used with care. See[Replace Resource Instead Of Applying Change](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#replace-resource-instead-of-applying-changes){:target="\_blank"}.

**Retry**: When selected, retries a failed sync operation, based on the retry settings configured:

* Maximum number of sync retries (**Limit**)

* Duration of each retry attempt in seconds, minutes, or hours (**Duration**)

* Maximum duration permitted for each retry (**Max Duration**)

* Factor by which to multiply the Duration in the event of a failed retry (**Factor**). A factor of 2 for example, attempts the second retry in 2 X 2 seconds, where 2 seconds is the Duration.

{::nomarkdown}

<br>

{:/}

Synchonize Resource options allow you to selectively sync application resources. You can bypass sync settings at the application level, and directly select the resources you want to sync, by state or otherwise.

* All resources regardless of their sync states

* Only out-of-sync resources

* Only selected resources

By default, Synchronize Resources displays and selects all resources in the application.

{% include

image.html

lightbox="true"

file="/images/applications/sync-manual-resources-form.png"

url="/images/applications/sync-manual-resources-form.png"

alt="Default settings for Synchronize Resources"

caption="Default settings for Synchronize Resources"

max-width="50%"

%}

You can search/filter resources using part of the resource names or regex strings, and then select the resources you want to sync.

For example, if you made changes to`api` resources or`audit` resources, type`api` or`audit` to locate the resources and then selectively sync those resources.

{% include

image.html

lightbox="true"

file="/images/applications/sync-manual-resource-search.png"

url="/images/applications/sync-manual-resource-search.png"

alt="Selective sync in Synchronize Resources"

caption="Selective sync in Synchronize Resources"

max-width="50%"

%}

{::nomarkdown}

<br><br>

{:/}

Perform on-demand app sync when needed.

**Before you begin**

Review:

*[Revision settings for application sync](#revision-settings-for-application-sync)

*[Additional options for application sync](#additional-options-for-application-sync)

*[Selective resource synchronization for application sync](#selective-resource-synchronization-for-application-sync)

**How to**

1. In the Codefresh UI, go to the[Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="\_blank"}.

1. Select the application to sync, and do one of the following:

* From the application's context menu on the right, select**Synchronize**.

* On the top-right, click**Synchronize**.

1. Select the**Revision** and**Additional Options** for the manual sync.

1. Click**Next**.

1. In**Synchronize Resources**, select the scope of the manual sync:

* To sync only specific resources, search for the resources by any part of their names, or define a Regex to filter by the required resources.

***All**: Sync all resources regardless of their sync state.

***Out of sync**: Sync_only_ resources that are`Out of sync`.

***None**: Deselect all resources.

{::nomarkdown}

<br><br>

{:/}

You can sync applications also using the Refresh and Hard Refresh options.

Argo CD maintains a cache of the application manifests in the Git repository. Both actions result in Argo CD syncing the application, the only difference being in the state of the cached manifests.

* Refresh: Compares the desired state in Git to the live state on the cluster, and syncs the desired state with the live state on detecting changes. Manifest cache is left unchanged.

* Hard Refresh: Also compares the desired state to the live state on the cluster, and syncs the desired state with the live state on detecting changes, and also replaces the manifest cache.

1. In the Codefresh UI, go to the[Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard){:target="\_blank"}.

1. Drill down into the application, and from the top-right, select**Refresh**, or click the context menu and then select**Hard Refresh**.

{% include

image.html

lightbox="true"

file="/images/applications/app-refresh-hard-refresh.png"

url="/images/applications/app-refresh-hard-refresh.png"

alt="Application sync with Refresh/Hard Refresh"

caption="Application sync with Refresh/Hard Refresh"

max-width="60%"

%}

[Creating applications]({{site.baseurl}}/docs/deployment/create-application/)

[Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/)

[Images in Codefresh]({{site.baseurl}}/docs/deployment/images/)