From b08ad5fe3752bf236cea68fd0a98d9b3e818028e Mon Sep 17 00:00:00 2001 From: Luana Dos Santos Date: Tue, 2 Sep 2025 12:59:40 -0300 Subject: [PATCH 1/2] W-19419968-replica-statuses --- cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc b/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc index c742917b..40edeceb 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc @@ -33,7 +33,7 @@ include::partial$select-private-space.adoc[tag=clickSettings] . Click *Configuration* to display the app configuration history: + Config changes tab:: -Displays the changes to the successfully deployed application configuration and includes the last ten configuration deployments in order by configuration date. +Displays the changes to the successfully deployed application configuration and includes the last ten configuration deployments in order by configuration creation date. A unique hash identifies each configuration in the history. All changes tab:: Displays a history of versions created from the configuration deployment and the actions performed on each version. @@ -49,7 +49,7 @@ Displays a history of versions created from the configuration deployment and the A message appears at the top of the page indicating the configuration is in progress. . Click *View status* to view the <> for each replica in the deployment. -When the configuration is successfully applied and deployed, a message appears at the top of the page, with application status, configuration identifier, date, and replica status. +When the configuration is successfully applied and deployed, a message appears at the top of the page, with application status, configuration identifier, completed date, and replica status. The new configuration appears in the *Config changes* list. If the configuration updates fail to deploy, the message indicates that CloudHub 2.0 didn't apply the configuration, the configuration status is `Update failed`, and the configuration appears in the *Config changes* history without a label. From 3050d56e26002871386f7f94c93a4a96e03ac2de Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Tue, 2 Sep 2025 13:59:58 -0300 Subject: [PATCH 2/2] Update ch2-update-apps.adoc --- cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc b/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc index 40edeceb..26aa5613 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-update-apps.adoc @@ -33,10 +33,10 @@ include::partial$select-private-space.adoc[tag=clickSettings] . Click *Configuration* to display the app configuration history: + Config changes tab:: -Displays the changes to the successfully deployed application configuration and includes the last ten configuration deployments in order by configuration creation date. +Shows the changes to the successfully deployed application configuration and includes the last 10 configuration deployments in order by configuration creation date. A unique hash identifies each configuration in the history. All changes tab:: -Displays a history of versions created from the configuration deployment and the actions performed on each version. +Shows a history of versions created from the configuration deployment and the actions performed on each version. . Depending on the deployment target (shared or private space), change the deployed configuration: + ** Specify runtime options, such as uploading a new application file or changing the deployment target and resource allocation.