kapp
hoogle
Our great sponsors
kapp | hoogle | |
---|---|---|
7 | 60 | |
852 | 714 | |
1.1% | - | |
8.1 | 6.3 | |
7 days ago | about 2 months ago | |
Go | Haskell | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kapp
- HELM vs KUSTOMIZE
-
How to handle the lifecycle of multiple COTS
If you want to take it one step further: you might be applying several resources at a time that are logically one "application". kapp (https://carvel.dev/kapp/) lets you group those together and give them a name, and provides a "terraform-like" experience where it shows you its execution plan before applying updates. So then you might do `ytt -f | kapp deploy -a name-of-thing` Or you could use helm's templating engine but then still pass the resulting yaml to kapp for its unification of the deployment step.
-
Dhall: A Gateway Drug to Haskell
since you mentioned Kubernetes...
> It would be nice if there was a separate state reconciliation system that one could adapt to use with Cue or Dhall or any other frontend
this exactly was thinking behind https://carvel.dev/kapp for Kubernetes (i'm one of the maintainers). it makes a point to not know how you decided to generate your Kubernetes config -- just takes it as input.
> In particular the ability to import other files as semantic hashes seems like a great feature.
it's an interesting feature but seems like it should be unnecessary given that config can be easily checked into git (your own and its dependencies).
-
Terraform should have remained stateless
i think kubernetes is not a great example in favor of more client state (like tf) since k8s has uniform resource structure (metadata.*) and first class labeling support. but as you point out kubectl doesnt use labels well (at least imho).
when building https://carvel.dev/kapp (which i think of as "optimized terraform" for k8s) the goal was absolutely to take advantage of those k8s features. we ended up providing two capabilities: direct label (more advanced) and "app name" (more user friendly). from impl standpoint, difference is how much state is maintained.
"kapp deploy -a label:x=y -f ..." allows user to specify label that is applied to all deployed resources and is also used for querying k8s to determine whats out there under given label. invocation is completely stateless since burden of keeping/providing state (in this case the label x=y) is shifted to the user. downside of course is that all apis within k8s need to be iterated over. (side note, fun features like "kapp delete -a label:!x" are free thanks to k8s querying).
"kapp deploy -a my-app -f ..." gives user ability to associate name with uniquely auto-generated label. this case is more stateful than previous but again only label needs to be saved (we use ConfigMap to store that label). if this state is lost, one has to only recover generated label.
imho k8s api structure enables focused tools like kapp to be much much simpler than more generic tool like terraform. as much as i'd like for terraform to keep less state, i totally appreciate its needs to support lowest common denominator feature set.
common discussion topics:
-
Deploy Neo4J's APOC plugin with code thanks to CARVEL vendir
kapp - Install, upgrade, and delete multiple Kubernetes resources as one "application"
-
Open Application Model – An open standard for defining cloud native apps
I really like this approach for simplifying Kubernetes. A few projects similar to OAM in that it provides a higher level "Application" CRD:
hoogle
- The Hunt for the Missing Data Type
-
What Is Dimensional Analysis?
Dimensions behave somewhat like a "type system" for math. These dimensional-analysis tricks act like the trick you see in Haskell sometimes, where you can easily guess an implementation of an expression once you know it's type (or e.g. search by type signature https://hoogle.haskell.org/ )
-
Java 20 Is Out
Ideally like this: https://zio.dev/reference/#concurrency
-
Haskell IDE setup
{ "customLocalFormatters.formatters": [ { "command": "make format", "languages": ["haskell"] } ], "emeraldwalk.runonsave": { "commands": [ { "match": "*.hs", "isAsync": true, "cmd": "make retag retag_file=${file}" } ] }, "ghcid.command": "make ghcid", "goto-documentation.customDocs": { "hs": "https://hoogle.haskell.org/?hoogle=${query}" } }
-
Idris: A Language for Type-Driven Development
You had a look at Hoogle?
For some type signatures there is (are) only one (or only a few) meaningful implementation(s).
-
Haskell is the one of the most hardest code
I'm in the middle on operators. I like being able to define my own, but I understand how it's challenging to figure out what the hieroglyphics mean when you're not familiar with them. https://hoogle.haskell.org/ can be a help here
-
What’s so great about functional programming anyway?
> In something like Haskell I need to know upfront what I may do with some "object". The IDE can't help me discover the methods I need. All it can do is to show me all available functions in scope.
Sorry, but this just isn't true. Hoogle <https://hoogle.haskell.org/> searches function by type, fuzzily: ask for functions whose first parameter is the type of the object-like thing, and you'll get just what you're looking for. And it's perfectly possible to run hoogle locally and integrate it with your editor.
Now, the tooling for a language like Java have had several centuries more of aggregate development work done on them compared to Haskell's tools, and if that polish is a difference-maker for you, that's fine! But it's not a fundamental limitation, and claiming it is is just fud.
-
Type-Signature.com
In my perusals into the Haskell ecosystem, discovering Hoogle[1] was definitely a revelation on the power of a strongly-typed language. Sometimes, you know the _shape_ of the thing you are looking for, but not the name. The ability to search a repository of packages for all functions conforming to a certain type signature (e.g., (a -> Bool) -> [a] -> [a]) is a superpower.
which is quite a bit more readable. You can even search Hoogle for x -> HashMap x y -> y and find it, try it!
https://hoogle.haskell.org/?hoogle=x%20-%3E%20HashMap%20x%20...
-
What Operators Do You WISH Programming Languages Had? [Discussion]
Haskell has hoogle, which searches Hackage for functions matching names, type signatures, etc.
What are some alternatives?
kubevela - The Modern Application Platform.
castle - A tool to manage shared cabal-install sandboxes.
argo-cd - Declarative Continuous Deployment for Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
ghci-ng
hakyll - A static website compiler library in Haskell
ihaskell - A Haskell kernel for the Jupyter project.
Exercism - Scala Exercises - Crowd-sourced code mentorship. Practice having thoughtful conversations about code.
merlin - Context sensitive completion for OCaml in Vim and Emacs
elm-make
kapp-controller - Continuous delivery and package management for Kubernetes.
hfd - Flash debugger with haskeline interface