Joe Julian

Can you provide a link to the charts? I'd be interested in seeing what's happening.

Looks like this behavior comes from https://github.com/helm/helm/blob/292368a64d6c9794b4573afa5a8dc6e940a21045/pkg/kube/client.go#L423 Since changing this to foreground (which I personally feel should have been the default when using the wait flag) will change existing behavior,...

That's my opinion, yes.

> It does not seem like the change will cause breakage in existing deployment; as no scenario seems to depend exclusively on --wait's current behaviour. This software has been in...

Also if you need any help, normally I'd suggest coming to the developer meeting but this week is cancelled because most everyone's at Kubecon. Next week should be good though.

I'm just not getting this. Could you perhaps reword this as a use-case?

I just noticed I was pinged on this back in April. Sorry, the triage maintainers just triage issues. We have no :heavy_check_mark:'s to give.

Yes, the project does need more maintainers. The first step (✔️), contribute code. Come join the developer meeting, if you can: https://github.com/helm/community/blob/main/communication.md#meetings. Post your interest in becoming a maintainer on...

Keep in mind we can't change existing behavior of commands. That would break a lot of other users workflows.

Sorry, let me phrase that better. Any changes to existing commands will need to adhere to [HIP 0004: Define and document the backwards-compatibility rules that apply to Helm minor and...