bug: stale instance entries accumulate in config when container is recreated

[Syedowais312]

Describe the bug

Description

When a container is removed externally (e.g. docker stop && docker rm) and
microcks start recreates it, the old instance entry is never removed from config.
A new entry is appended instead, causing duplicate instance records to accumulate.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

Steps to Reproduce

1. ./microcks start
2. docker stop microcks && docker rm microcks
3. ./microcks start
4. cat ~/.config/microcks/config two instance entries with same name but different container IDs

Screenshots

Root Cause

RemoveInstance matched by Name instead of ContainerID. Since the recreated
container has a new ID, UpsertInstance never finds a match and always appends.

Microcks version or git rev

No response

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

No response

Additional information

No response

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️