Cue Alternatives
Similar projects and alternatives to cue
-
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
-
-
-
garden
Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching.
-
-
cue
The new home of the CUE language! Validate and define text-based and dynamic configuration (by cue-lang)
-
-
steampipe
Use SQL to instantly query your cloud services (AWS, Azure, GCP and more). Open source CLI. No DB required.
-
-
-
-
-
starlark-go
Starlark in Go: the Starlark configuration language, implemented in Go
-
-
-
-
Reviews and mentions
- The Perfect Configuration Format? Try TypeScript
- YAML: It's Time to Move On
-
Ask HN: What you up to? (Who doesn't want to be hired?)
I'm continuing to work on https://concise-encoding.org which is a new security-conscious ad-hoc encoding format to replace JSON/XML and friends. I've been at it for 3 years so far and am close to a release.
In a nutshell:
- Edit in text, transmit in binary. One can be seamlessly converted to the other, but binary is far more efficient for processing, storage and transmission, while text is better for humans to read and edit (which happens far less often than the other things).
- Secure by design: Everything is tightly specced and accounted for so that there aren't differences between implementations that can be exploited to compromise your system. https://github.com/kstenerud/concise-encoding/blob/master/ce...
- Real type support because coercing everything into strings sucks (and is another security risk and source of incompatibilities).
XML had a good run but was replaced by JSON which was a big improvement. JSON also had a good run but it's time for it to retire now that the landscape has changed even further: Security and efficiency are the desires of today, and JSON provides neither.
I've got the spec nailed down and can finally see the light at the end of the tunnel for the reference implementation in golang. I still need to come up with a system for schemas, but I'm hoping that https://cuelang.org will fit the bill.
-
No YAML
Has anyone taken a look at Cue who can share any experiences?
It's mentioned on the site as an alternative to Yaml. Recently watched (~half of) this intro to it: https://youtu.be/fR_yApIf6jU
- Ask HN: Is there a good way to run integration tests on Kubernetes?
-
Cue: A new language for data validation
the most interesting summary explanation of cue lang and its differences is from a bug filing - https://github.com/cuelang/cue/issues/33
>CUE is a bit different from the languages used in linguistics and more tailored to the general configuration issue as we've seen it at Google. But under the hood it adheres strictly to the concepts and principles of these approaches and we have been careful not to make the same mistakes made in BCL (which then were copied in all its offshoots). It also means that CUE can benefit from 30 years of research on this topic. For instance, under the hood, CUE uses a first-order unification algorithm, allowing us to build template extractors based on anti-unification (see issue #7 and #15), something that is not very meaningful or even possible with languages like BCL and Jsonnet.
-
CMake proposal: Unified way of describing dependencies of a project
I agree with you. Personally, I think Cue is much better than either YAML, TOML or JSON because it adds the concept of types to the idea of describing configuration.
-
Cloud Infrastructure as SQL
true, but the tooling and workflow remains the same.
Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config.
I'm exploring using CUE (https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer
- Ask HN: What open source projects are you working on and why?
-
Tgen: A template tool a la Helm or Consul Templates
I've been using https://cuelang.org for any configuration / yaml like generation. This link has a GH search with two discussions that talk about Rego: https://github.com/cue-lang/cue/search?q=rego&type=discussio...
I wrote https://github.com/hofstadter-io/hof to use this concept "at scale", i.e. inputting & outputting multiple files & dirs. The main idea was to generate common code across the stack from a single-source-of-truth. Today it inputs CUE only, which has all the things needed to validate the incoming data and also contains the templates, so `hof gen` takes the same args as `cue export`. It uses diff3 so that you can regenerate the output after modifying the input or the generated content, which is something I needed so that when I fill in the generated API handler func, and then change the design a bit, that I can keep the manual work.
-
YAML and Configuration Files
I think Cue[1] is a much more powerful and useful config format that also has the ability to generate validated JSON or YAML if needed.
[1]: https://cuelang.org
-
evaluating dagger - programmable CI/CD tool
The language they used is called Cue, it was created by an ex-googler who created the GQL. Dagger allows to embed any script anywhere inside your cue config. The scripts are then executed transparently inside a container. Also it's being built by the former docker team.
Stats
cuelang/cue is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.