Dex

Pretty sure this has to do with cloning to a tmp dir under installer, and then moving that dir somewhere else. I got this error in the UI and realized...

Hi @nictrix! Thanks for the detailed write up. I think you're right, this is a great feature request that I'd like to see as well. I think there's two or...

Following up on this @laverya -- I think right now when you do `ship init github.com/istio/chart/tree/v.1.1.0/some/chart/path`, it gets translated `ship init github.com/istio/chart/tree/__latest__/some/chart/path`. If we were to implement proper locking, that...

Yeah having it be opt in makes this really easy to get started solving. Off the top of my head, `ship update --lock` makes sense to me, as does `ship...

what happens if I `ship init github.com/istio/chart/tree/v.1.1.0/some/chart/path` in the lock-capable world? Do I still get auto-updated to v1.2.0 if it exists?

Want to give a quick update on this issue with the state of discussion and some workarounds. It looks like there are two things at play here: - missing alias...

Having an alias section on the values page is probably an appropriate alternative to `4`, perhaps a `4b`. The reason to make a discrete step would be if the UI...

Hi Greg -- thanks for submitting an issue! I'm sorry you've run into this. I think we could definitely use a little bit of better messaging around this. It looks...

@laverya do you want to check out those `ship init` targets and we can brainstorm some ways to detect this error? Maybe something like "if upstream contains `chart` or `helm`,...

Thanks for opening this issue @Timoses and for giving Ship a spin. I was able to reproduce this, looks like the default Rook chart doesn't ship with a values.yaml as...