Nikolai Emil Damm

I was thinking of something in line with a boolean called `ignoreExistingFiles`. If it is set to true the action will not copy a file that exists, and if not...

Hmm, really good idea! I thought about this once but I was not able to come up with a good solution, as one could potentially want to initialize multiple clusters...

> If not, look for a config file (cluster) with the same name as the folder. The problem with this is that there could be: ``` cluster1-ksail-k3d-config.yaml cluster2-ksail-k3d-config.yaml k8s/clusters/cluster1/** k8s/clusters/cluster2/**...

It will contain one cluster name. See it as a per-project configuration. One folder should not contain more than one ksail cluster. In rare cases where there could be more...

That would be cool! If an in-UI option is supported along with some way to notify me when I am not looking at the UI, I am a happy man....

I totally understand that! I am thinking it should be opt-in, and that the functionality around upgrading kubernetes version and talos version should support rollbacks in either case before this...

Annoying it is an enforced limitation by Apple. There might be edge cases they do not want to maintain support for, but I doubt it 😕 Back to waiting for...

I will be implementing a disable for in-place as an arguement. I still believe the default should be to decrypt in-place. I am thinking something in terms of: `ksail sops...

You are right. I was thinking of this functionality, which I want to be the default:

But maybe it makes sense to add a specific arguments in this case? `ksail sops edit ` Opens your $EDITOR to edit the file in-place. This is what I envisioned...