Decoupling of the referenced helm chart

[DimitarHKostov]

Decoupling of the referenced helm chart

[jakobmoellerdev]

This requirement was rejected multiple times because we discourage the soft references via url. This can be bad because the content behind the URL might change or get removed. This is a problem because suddenly your module version is broken without you realising it. Thus I am closing this issue and we will not pursue this.

[manolvalchev]

we discourage the soft references via url.

@jakobmoellersap, The fundamental point in the request is to allow reference of charts (resources in general) from an external repo and not force people to produce duplicate charts (resources in general) in many repos. What problem do you see in referencing released charts (resources in general), e.g. version 1.2.3?

[jakobmoellerdev]

By referencing released charts in URLs you have to make sure the URL is always available and usable. While this is ensured by bundling it into the Module with the kyma CLI, we cannot ensure these guarantees when you are using external references. They are fundamentally not part of our integrity guarantees that we deliver when bundling the chart via OCI image layer. If this is acceptable to you I suggest we add an unsafe mode instead that we can enable and then also support more layer types with external references. WDYT?

[jakobmoellerdev]

I want to emphasise that you do not need double maintenance to correctly bundle your module. Instead you just should not check it out into the operator repository but pull it in a make target. that way during bundling you will still ensure one unique chart version while you can maintain your chart elsewhere.