Building #Regal’s linter rules in #Rego really pushed the language to its limits some years back, and both OPA and Rego have improved a lot thanks to that. Building parts of its *language server* in Rego too was perhaps taking it too far, but OTOH, the LSP is really just JSON in and JSON out, which is what OPA does best after all.

The bundled policies in Regal are normally embedded in the binary. That’s great for distribution, but kinda sucks for development as any change requires compilation. Not anymore! Today I merged some work of mine allowing live-reloading of the language server policies, and it’s such a *huge* difference seeing the result of a change a second after you made it. The video here shows live-editing of a LSP code action policy, and how adding a new “source action” item in the server immediately propagates to the client. Sooo much fun!

"Our policy as code, temporarily disable OPA" 🤣

I guess that means we've made it.

https://www.youtube.com/watch?v=rXPpkzdS-q4

Anyone going to https://events.linuxfoundation.org/open-source-summit-europe/ ? If you want to talk about #opa or #backstage I love yappin about both 🤓

#oss #opensource

🚨 Security doesn't start in prod — it starts at terraform plan.

With Policy as Code tools like #OPA, #Checkov, Snyk, and #Sentinel by HashiCorp, you can catch misconfigs before they deploy. 🛡️

🎥 https://youtube.com/shorts/C-2OJMFVz8c

#Terraform #HashiCorp #DevSecOps #PolicyAsCode

A new version of #Regal is out! v0.34.0 of the #OPA community's favorite linter and language server brings you 3 new linter rules, much faster linting, and many improvements and fixes. And all for the price of nothing! Check out the release notes, get your copy and get linting!

https://github.com/StyraInc/regal/releases/tag/v0.34.0