Automatic Instance Renaming Before Expunge

[baltazorbest]

Hello.

Description:
Introduce an automatic renaming mechanism for instances marked as deleted (before the expunge process). When a user deletes an instance, CloudStack could automatically append a timestamp to its name — for example, renaming Backend to Backend-20251006.

Problem:
After a user deletes an instance, it remains in the system (until expunge) but is no longer visible to the user. During this period, if the user tries to create a new instance with the same name, an error occurs because the old record still exists.

Proposed Solution:
At the “delete” operation step, automatically rename the instance by adding a timestamp suffix.

Example workflow:

1. User creates an instance named Backend.
2. User stops the Backend instance.
3. User deletes the instance — the system renames it to Backend-20251006.
4. The user can now immediately create a new instance named Backend without error.

Benefits:

1. Prevents naming conflicts after deletion.
2. Improves user experience and clarity.
3. Requires minimal implementation effort (simple rename before expunge).

[DaanHoogland]

sounds good @baltazorbest , I am not sure of any unexpected side effects (like when recovering the VM) so I think it should be beind a feature flag.