Open phillebaba opened 3 months ago
The easy solution to this problem is to just to check if state is nil before the other state check. I do however think it is slightly weird to delete a k3s cluster blindly without any user input just because the scripts are located at a specific file location.
Environment
Device and OS: Arch Linux App version: v0.35.0 Kubernetes distro being used: N/A Other:
Steps to reproduce
zarf destroy --confirm
against a cluster where Zarf is not installed.Expected result
The command should either error or should exit immediatly.
Actual Result
Panics due to a nil pointer in the state.
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Low/Medium
Additional Context
N/A