harmony
Easily test downstream projects before releasing new code (by hofstadter-io)
cuelm
Experiments with CUE on the quest to reimagine devops-ops. (by hofstadter-io)
harmony | cuelm | |
---|---|---|
1 | 2 | |
14 | 32 | |
- | - | |
1.0 | 3.3 | |
about 1 year ago | 9 months ago | |
CUE | CUE | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
harmony
Posts with mentions or reviews of harmony.
We have used some of these posts to build our list of alternatives
and similar projects.
-
$100M stolen from the Harmony bridge
I have hopes this one will go away so my own Harmony project, for testing downstream projects against changes before releasing, can be the better harmony in search.
https://github.com/hofstadter-io/harmony
cuelm
Posts with mentions or reviews of cuelm.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-16.
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
We've started working on a tool to use CUE to create a single config space across TF, Helm, and other tools in the devops space.
https://github.com/hofstadter-io/cuelm
Our hypothesis is that a unified config space across our industry will bring many benefits.
Our open questions are largely around whether we
(1) replace / alternative
(2) just a skin, still same reconciliation loop from the tools
(3) replace, but support existing modules & charts
-
HashiCorp: Terraform-config-inspect: A library for inspection of TF configs
Thanks for the share! Very timely
We are in the process of introspecting TF to produce CUE schemas. Maybe this can help us cuetify user TF as well
if you are curious: https://github.com/hofstadter-io/cuelm (it has expanded in scope since inception to include the likes of TF and other areas of e2e CI)