Doc: missing good examples of high level interface definitions

[PierreR]

I would argue that working with dhall-kubernetes directly will not provide substantial advantages over other competitive products.

On the other hand, building on the foundation of this repository, an end user can provide higher abstractions by taking advantage of the dhall language.

Unfortunately, I don't believe there is a lot of public examples that show how to pave the way. Worse the generated code from this repository (or others such as dhall-packages) is actually misleading, full of indirections and difficult to read.

This issue is about providing links to such high level repositories. I believe it could help a lot to raise the adoption of dhall-kubernetes.

[Gabriella439]

@PierreR: What if we were to link to https://github.com/dhall-lang/awesome-dhall and then add a Kubernetes section to that?

[PierreR]

Thinking about this a bit more, I believe the high level definitions I am talking about is more or less what charts are for Helm.

So in Helm you will have a way to discover if someone have already written a chart for - let say Logstash - in the helm hub or directly in the code source.

I looks a bit counter-intuitive to me to place these high abstractions into https://github.com/dhall-lang/awesome-dhall. I believe dhall-kubernetes should be the place where such abstractions are exposed as it is the case with Helm.

If you go and have a look at the helm website, Charts are the third items on the menu after "Home" and "Documentation".

[PierreR]

@Gabriel439 for what it worths, this is a place my team could contribute openly to enforce the dhall-kubernetes ecosystem

[Gabriella439]

@PierreR: I do think there should be a central repository for organizing the Dhall analog of Helm's charts, but my impression was that dhall-packages was slowly becoming that repository

This repository should probably stay minimal, though, but we can link to any other repository that does provide charts for discoverability

[PierreR]

@Gabriel439 dhall-packages has a couple of issues:

• it looks inactive (see: Is '--omit-empty' still required for argocd ? EarnestResearch/dhall-packages#62)
• it is not clear which version of dhall-kubernetes is used; it makes you believe it would work with the latest (which is not true).
• it looks like it is still using a version of dhall-kubernetes that does not support multiple kubernetes versions

dhall-packages currently does not work unless you happen to use the exact same kubernetes version (15.0.0) together with the exact same dhall-kubernetes version (it is unclear what this version actually is).

We are using argocd from dhall-packages and we had to make our own fork.

I believe a Dhall analog of Helm's charts should be integrated in the Dhall organization otherwise it worths nothing.

[PierreR]

My understanding is that most of dhall-pakages is generated from an APIs. It could be the equivalent of dhall-kubernetes but for other tools related to the k8s ecosystem such as argocd, openshift, ...

That is not what Helm charts are about. Helm charts would ease the kubernetes deployments for quickly deploying applications (such as postgres, elk, ...) within a Kubernetes cluster.

I haven't seen such equivalent for Dhall so far.

[Gabriella439]

@PierreR: Ah, I see. Yeah, then I guess we still need a repository for the "Dhall equivalent of Helm". I started something like that a while back here:

• https://github.com/Gabriel439/dhall-kubernetes-charts

… but then I realized I was going about it wrong because I was trying to translate Helm to Dhall as literally as possible instead of doing something more idiomatic to Dhall.