Decommissioning services #426
No reviewers
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal!426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "95-decommissioning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements service decommissioning, closing #95.
On admin action, we call the k8s API, but we do not wait to confirm full deletion. This is not 100% in line with the issue text, but waiting like that might lead to timeouts / would potentially require adding some long polling or HTMX to the admin page in question. Very doable, but wanted to check first if that was necessary / intended.
Tested, looks good. I think the currently implemented behavior makes sense.