[Feature Request] Implement the function to archive the stacks #653

New Issue

GiteaMirror · 2025-10-31T15:17:12-05:00

GiteaMirror commented

2025-10-31 15:17:12 -05:00

Originally created by @andreazorzi on GitHub (Oct 31, 2025).

Implement the ability to archive stacks, for example destroyed stacks.
For example, on my server I have some stacks that I no longer use, and I've destroyed them, but having them in the stack list, besides "taking up space", it can happen that they get selected by mistake if I need to perform bulk actions.
However, I don't want to delete them because for one reason or another I might need to restore them.
Currently what I do is copy the stack's toml code, save it locally on my PC and then delete the stack, so that I can reactivate it in the future.
Since I haven't figured out if it's possible to import a toml file and if so where it can be done, it would be really useful to have the ability to archive stacks and then be able to reactivate them when needed.

Thank you

Originally created by @andreazorzi on GitHub (Oct 31, 2025). Implement the ability to archive stacks, for example destroyed stacks. For example, on my server I have some stacks that I no longer use, and I've destroyed them, but having them in the stack list, besides "taking up space", it can happen that they get selected by mistake if I need to perform bulk actions. However, I don't want to delete them because for one reason or another I might need to restore them. Currently what I do is copy the stack's toml code, save it locally on my PC and then delete the stack, so that I can reactivate it in the future. Since I haven't figured out if it's possible to import a toml file and if so where it can be done, it would be really useful to have the ability to archive stacks and then be able to reactivate them when needed. Thank you

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#653