bcl
go-plugin
bcl | go-plugin | |
---|---|---|
7 | 30 | |
14 | 5,006 | |
- | 1.9% | |
9.5 | 6.3 | |
7 days ago | 11 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
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.
bcl
-
HCL: Toolkit for Structured Configuration Languages
Another take on replacing HCL with something more sensible:
BCL https://github.com/wkhere/bcl
-
Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
I agree with you that HCL sucks when it comes to variables.
Other thing that is funny: no user-defined functions, being unable to use function calls in string interpolations, but allowing variables... so it is like saying: we have this parser and at some points it allows expressions, at some other point not. This seems wrong.
At the same time I agree or at least understand original author's intent to squeeze HCL to maxinum. There is something appealing in HCL visual form, at least when defining resources. Maybe it's just (almost) simplest form of defining such structures that can exists.
This is why I started to work on my own format for configuration, visually similar but with different model of evaluation.
Here is the first attempt: https://github.com/wkhere/bcl
Disclaimer: I named it BCL, 'B' stands for Basic, to somehow relate to HCL and make it easily pronounced. But later I discovered that another BCL is used as Google to configure the Borg platform and seems to be massively hated ;) So I look for the better name..
-
Ask HN: Show me your half baked project
I am crafting BCL, own configuration language.
https://github.com/wkhere/bcl
I started this when I was unable to squeeze certain usage patterns from HCL, like: variables living in the same scope as the file, evaluating variables in one pass with parsing, easily using external (environment) variables; plus, a simplified syntax.
The implementation is mostly done: you can defined blocks holding key-value pairs and use numerical, string and bool expressions in them. I will add lists and nested blocks.
At this very moment I am rewriting a parser from yacc-based to a Pratt top-down parser with vm, heavily inspired by the excellent book "Crafting Interpreters".
-
That's a Lot of YAML
https://github.com/wkhere/bcl
Will not immediately help for all of YAML usages, but at least for defining resources in a Terraform-like style. In fact, it's already it's already helpful as a replacement for HCL in one internal project, that was a final motivation to hack it.
In a bigger picture, I have no idea how to help with YAML omnipresence in Kubernetes. More than a half of my problems in a $daily_job is how crude is consolidating a final Helm chart from different sources. I am not saying that Helm would be inherently a bad tool or my company has chosen pretty bad way of using it - I guess everyone is doing their best considering the ciscumstances. But manipulating textual templates is just too error prone, and the detection of errors happens too late. I dare to say - Kubernetes would do much better with custom format based on a C-like syntax, instead if trying to prove how cool YAML is, especially when it isn't.
- BCL - a simplified HCL-like configuration format (WIP)
-
What Is Wrong with TOML?
Related:
just few days ago I crafted together some ideas i had couple of years already for a configuration language, syntactically like HCL but without HashiCorps idiosyncrasies.
Here it goes, BCL (_Basic_ Configuration Language, for a lack of better name yet), Go prototype, I can code Python port and possibly several other as well..
https://github.com/wkhere/bcl
go-plugin
-
Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.
Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.
[1]: https://github.com/hashicorp/go-plugin
- Show HN: Clace – Platform for secure internal web applications
- Wazero: Zero dependency WebAssembly runtime written in Go
-
referencing packages on the internet and using go plugin
I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).
- Can Go dynamically load library module at runtime?
-
Binary packages alternative
You'll never fully protect your code from someone who's dead-set on reverse-engineering it, however, you can use https://github.com/hashicorp/go-plugin or a similar RPC technique, which will let you ship binary plugins and will also be less fragile and janky compared to something made with `-buildmode=plugin`.
- Trying to build Rust Plugin System
-
How would you guys support plugins in a Go app? (or any other compiled language for that matter)
The plugin system that hashicorp uses for all their projects works very well. It's essentially a local RPC implementation. https://github.com/hashicorp/go-plugin
- Change go code behaviour at runtime
-
Is the documentation for making non-go plugins in the go-plugin repo outdated?
can you try older go-plugin versions? The only major change in v1.4.4 was a bugfix for automtls. https://github.com/hashicorp/go-plugin/blob/master/CHANGELOG.md