From 26f0ffc10b533775bcb2fdf730c07344521c0e9a Mon Sep 17 00:00:00 2001 From: Edward Ly Date: Tue, 12 Nov 2024 09:19:22 -0800 Subject: [PATCH] fix(admin): clarify default behavior for AppAPI unregister command Signed-off-by: Edward Ly --- admin_manual/exapps_management/ManagingExApps.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/admin_manual/exapps_management/ManagingExApps.rst b/admin_manual/exapps_management/ManagingExApps.rst index a3a914ab7..680bb6696 100644 --- a/admin_manual/exapps_management/ManagingExApps.rst +++ b/admin_manual/exapps_management/ManagingExApps.rst @@ -38,8 +38,8 @@ Unregister Command: ``app_api:app:unregister [--rm-data] [--force] [--silent] [--] `` -To remove an ExApp you can use the unregister command. -There are additional options to keep the ExApp persistent storage (data volume). +To remove an ExApp, you can use the unregister command. +By default, this command does *not* delete the ExApp's persistent storage (data volume) to avoid accidental removal of any user data. Arguments ********* @@ -50,8 +50,8 @@ Options ******* * ``--rm-data`` *[optional]* - remove ExApp persistent storage (data volume) - * ``--force`` *[optional]* - continue removal even if some error occurs. - * ``--silent`` *[optional]* - print a minimum of information, display only some errors, if any. + * ``--force`` *[optional]* - continue removal even if some error occurs + * ``--silent`` *[optional]* - print a minimum of information, display only some errors, if any Update ------