Yevhen Tienkaiev

This issue is critical! With this issue Kubernetes terraform module is useless in many cases. Why there no workaround yet? Is there any workaround available?

@cowtowncoder thank you, but keep in mind it will be cool if in `2.13` it will be possible to enable it by simple: ``` ObjectMapper objectMapper = new ObjectMapper(); objectMapper.configure(DeserializationFeature.RELAXED,...

cc @int128

Keep in mind that official docs not reflect real useful functionality that they support in source https://github.com/argoproj/argo-cd/blob/f0b03071fc00fd81433d2c16861c193992d5a093/common/common.go#L186 I added comment in proposed changes about it

This is base, strange that it's not added initially. It's pretty useless right now, since there nice helm chart https://artifacthub.io/packages/helm/piraeus-charts/snapshot-controller that can be used in conjunction with terraform

Pretty actual, it's appear to be a blocker to enable native sidecars for istio as sidecars now can't work properly with Argo Rollouts. This one is critical to release

yes, it's basic thing. Otherwise you just set ignore everything, but it means that you can miss real error

+1 this is critical feature for Dev Environments adoption

@bastianb I got question why it's closed? Actually I believe this issue tracker is for this feature  https://docs.docker.com/desktop/dev-environments/ So we need a button that will re-scan `compose-dev.yaml` and update...

@maartenba , @rumpl did you connected internally? Heavy need this=) Here motivation post for JetBrains on LinkedIn https://www.linkedin.com/posts/martinmarcher_jetbrains-intellij-pycharm-activity-6976145178717769729-t1wW?utm_source=share&utm_medium=member_desktop