Skip to content

Conversation

@oleksandr-nc
Copy link
Contributor

Fixes #624

When the occ app_api:app:unregister command fails to remove a container (e.g., because it was already deleted manually), users are now shown a helpful hint suggesting the --force option to continue unregistering.

The hint includes the container name for easier manual verification/cleanup.

Before:

  Failed to remove ExApp my_ex_app container

After:

  Failed to remove ExApp my_ex_app container
  Hint: If the container "nc_app_my_ex_app" was already removed manually, you can use the --force option to continue unregistering.
  

Co-authored-by: Anupam Kumar <[email protected]>
Signed-off-by: Oleksandr Piskun <[email protected]>
oleksandr-nc and others added 2 commits January 14, 2026 13:53
Co-authored-by: Anupam Kumar <[email protected]>
Signed-off-by: Oleksandr Piskun <[email protected]>
Co-authored-by: Anupam Kumar <[email protected]>
Signed-off-by: Oleksandr Piskun <[email protected]>
Copy link
Collaborator

@kyteinsky kyteinsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@oleksandr-nc oleksandr-nc merged commit 1f7af37 into main Jan 14, 2026
34 checks passed
@oleksandr-nc oleksandr-nc deleted the fix/hint-force-option-unregister branch January 14, 2026 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a hint about the --force options when unregistering an app

3 participants