Igor Zibarev

Wow that's a real number. I agree that the plugin was never designed to handle such volumes, and there is definitely a room for improvement. Out of curiosity, why do...

Hello! Is this still actual for you? Could you provide the helm and helm-s3 versions you use?

Yeah, that's an interesting feature. Of course, the design and proper implementation of this feature are very important, as this directly affects user privacy and security.

@flowchartsman Awesome work, thanks! I would also like to give some love to this tool and dip my fingers in the code when I can find time 🙂

I don't think that helm-s3 is affected directly, because the vulnerability takes effect when some other malicious plugin added to helm installation. However, will update helm package we use for...

Fixed in https://github.com/hypnoglow/helm-s3/pull/439

Hi, http(s) is already supported, see: https://helm-s3.hypnoglow.io/docs/advanced-features/#serving-charts-via-http What is the motivation of the proposed change?

@sonjek > Therefore, this change allows to write an absolute path with the https protocol (like helm repo index). I see the effect, but I don't understand the need yet....

We also use [bun](https://bun.uptrace.dev/) and would love to see support for `bun.Tx` and/or `sql.Tx`. Otherwise it seems impossible to integrate with existing transactions.

Hey @brandur Currently, we consider only `pgx` to be a viable driver. We switch old apps from `lib/pq`. And `bun` native driver has some problems that we don't have using...