Joe Julian

I seem to be failing at understanding this topic. Could you add the steps to reproduce an example of what you're asking so I can wrap my head around the...

Have you had a look at the [common.deployment](https://github.com/helm/charts/tree/master/incubator/common#commondeployment) example? I've never used it, myself, but it appears that it has some template that's missing from your description.

If I'm understanding correctly, this affects the `upgrade` and `rollback` processes due to the fact that when a StatefulSet or Deployment is updated, it's still considered `ready` because the subresources...

As for a proposal, that would start as a [HIP](https://github.com/helm/community/tree/main/hips).

Values are not processed as templates so no, that won't work. All I can think of is adding another field: ``` triggers: - type: azure-servicebus serviceBusNameRef: ["global","environment"] ``` Then using...

Seems reasonable. I think the only reason it's different is Erik missed it in [this PR](https://github.com/helm/helm/pull/7795)

To catch that, a dry-run would have to be server-side. Helm specifically does not do server-side dry-runs due to a perceived security issue. There has been discussion at https://github.com/helm/helm/pull/9426 with...

Correct. Helm does not have any way of parsing CRDs and comparing a resource with the definition of that CRD.

The tests are templated at the time of the chart installation and stored in the release secret. Could you just set the token during the install? ``` helm install my_release...

Best case, the 3rd party chart has a way to disable the creation of that configmap. If not, the best I've got is to use a post-install hook to use...