Bug: kusion destroy termination leads to a locked release file

[liu-hm19]

What happened?

The release file of a stack will be locked in the destroying phase if kusion destroy command terminates accidentally, e.g. triggered by SIGINT or SIGTERM.

What did you expect to happen?

The release file should update its operation phase to failed.

How can we reproduce it (as minimally and precisely as possible)?

• Execute kusion destroy command
• Enter ctrl + c to terminate

Anything else we need to know?

No response

Kusion version

$ kusion version
# paste output here
releaseVersion: 0.12.0
gitInfo:
    latestTag: v0.12.0
    commit: 88c4a179f71eb67b710736434691423213013530
    treeState: clean
buildInfo:
    goVersion: go1.22.4
    GOOS: linux
    GOARCH: amd64
    numCPU: 4
    compiler: gc
    buildTime: "2024-06-12 12:48:49"

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools