SaaSHub helps you find the best software and product alternatives Learn more →
Cue Alternatives
Similar projects and alternatives to cue
-
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Pulumi
Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
starlark-go
Starlark in Go: the Starlark configuration language, implemented in Go
-
steampipe
Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
-
cue
The home of the CUE language! Validate and define text-based and dynamic configuration
-
-
hof
Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
-
-
-
-
-
terragrunt
Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
cue 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
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 28 Mar 2024
Stats
cuelang/cue is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of cue is Go.