migmartri
Joined 17 years ago
Karma
240
Submissions
26
Member since
Mar 4
Recent submissions
Comment · 1 year ago
Thanks for the write-up
What languages would you say are viable options in practice today to match rego(language and engine) functionality?
Comment · 3 years ago
I found this OSS tool interesting since it abstracts pretty much all the plumbing required to set up a computer vision pipeline.
Comment · 3 years ago
For some reason, the act of choosing a plugin mechanism for our new project has been presented in my head a dilemma. Not a clear winner between the built-in stuff (plugin stdlib), the boring but battle tested option (Hashicorp go-plugin [1]) and the new exciting shiny ("future proof?") object web assembly plugins [2]
I ended up choosing the "traditional" Hashicorp library but any feedback, or comments on why you might think I am making a terrible mistake would be appreciated :)
[1] https://github.com/hashicorp/go-plugin [2] https://github.com/WebAssembly/WASI/blob/snapshot-01/phases/...
Comment · 3 years ago
One step at the time. First, let's make something people love :)
Comment · 3 years ago
Thanks!
I am afraid I don't have a formed opinion on the sigsum project yet.
Thanks for the pointer though, it indeed looks interesting, it might come handy once we start the effort of adding a transparent log (i.e rekor) to Chainloop.
Comment · 3 years ago
Chainloop is not designed nor implemented with that centralization concept in mind.
It is meant to run as any other OSS infrastructure piece in your Software Supply Chain. The source of truth that we describe, it's about providing organizations with a single mechanism to define, ingest and route metadata and artifacts to their final destination (i.e artifactory, OCI registry, ...)
miguel at chainloop.dev