SaaSHub helps you find the best software and product alternatives Learn more →
Jsonnet Alternatives
Similar projects and alternatives to jsonnet
-
-
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
kube-libsonnet
Bitnami's jsonnet library for building Kubernetes manifests
-
-
Pulumi
Pulumi - Universal Infrastructure as Code. Your Cloud, Your Language, Your Way 🚀
-
-
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
-
cdk8s
Define Kubernetes native apps and abstractions using object-oriented programming
-
-
-
-
-
-
-
httpie
🥧 HTTPie for Terminal — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
jsonnet reviews and mentions
-
Cue Wins
Same as Jsonnet but it's only a small part of the picture. For someone who use JSON, I expect the adoption of CUE to be incremental but in reality I need to use CUE's own syntax to get the value out of it. Jsonnet was was closer to to the mindset that I have with that respect. Some context: https://github.com/google/jsonnet/issues/605#issuecomment-72...
-
The YAML Document from Hell
I wonder why generated JSON is not used more widely, something like jsonnet[0], although I've never used it.
Most systems come with Python 3 installed, which supports working with JSON[1] without installing any dependencies. So, I'm wondering if we could use Python to generate JSON data that is then consumed by other tools. This would fix the lack of comments and trailing commas in JSON, you get functions and other abstractions from Python, and you don't need to install any third-party tools (vs. something like jsonnet).
[0]: https://jsonnet.org/
-
What tech stack do you use at work? What's your favourite one?
fwiw, jsonnet was a breath of fresh air to help tackle our configuration complexity.
-
-🎄- 2022 Day 21 Solutions -🎄-
sed to generate a Jsonnet program for part 1:
-
Should i migrate from Kustomize to Helm?
We experimented with Jsonnet and Dhall as languages that allow you to compose structured text files rather than template then. With hindsight I can tell you that the supporting tooling (linting, testing, package management) never materialized for Jsonnet, and Dhall is too complex unless you have a lot of Haskell devs.
-
Nginx ingress controller: how to insert whitelist-source-range annotations globally, but conditionally at the same time?
You can do this sort of thing (and generally keeping everything DRY) by generating your manifests programatically. I use jsonnet (https://jsonnet.org/) to generate k8s manifests, but there are other tools...
-
Why We Use CUE (and Not Helm)
Jsonnet promises to be JSON plus templating, and that's exactly what it delivers. It allows you to include other files and has many useful features such as variables and functions. Jsonnet overall was a pretty decent experience, and we could've stopped there.
-
Managing multiple repos
You can use JSONNET and 'std.parseYaml' function for more precision tuning.
-
We want to make Nix better
> To seriously answer the question: is the Nix language required for the Nix packaging system to exist? Laziness is required, to some degree, but can the next iteration provide an on-ramp which doesn't involve learning a new lang and paradigm? Guix folks sure think so.
I'd love to hear from someone deeply familiar with Nix and Guix about laziness.
I'm deeply familiar with Nix and I've concluded that lazy semantics is absolutely critical for a configuration language. It lets me refer to other attributes of my configuration from anywhere. For example, I can refer to port number from my whatever service in my firewall. Nix's system of overlays depends on laziness too to provide efficient late-binding familiar from OOP.
I don't need to topologically sort the evaluation of the various inter-dependencies of my configuration. So long as there exists an evaluation order, laziness finds it.
Laziness is compelling enough that I managed to convince the author of Jsonnet <https://jsonnet.org/> of it when he was designing it, and in turn he helped me design what is now known as overlays in Nix.
I don't even understand how Guix manages to work without laziness, though clearly it does somehow. I'm curious as to how that is possible, though I fear I will only ever truly understand by diving into Guix.
-
Falling for Kubernetes
> As an aside, the existence of the '{{ | indent 4 }}' function in helm should disqualify it from any serious use. Render, don't template.
This. My first thought when I saw the indentation hack was "it can't be a serious, production-ready software".
My take on this is as follows.
If you have a simple use case, write your K8s manifests directly.
If you have a complex use case, Helm is often more pain than its worth. Use alternatives, for example Jsonnet[0] with kubecfg[1]. Or emit manifests from your language of choice. Just don't use Helm.
[0]: https://jsonnet.org/
-
A note from our sponsor - #<SponsorshipServiceOld:0x00007fea59942b68>
www.saashub.com | 4 Feb 2023
Stats
google/jsonnet is an open source project licensed under Apache License 2.0 which is an OSI approved license.