Brutkey

Anders Eknert
@anderseknert@swecyb.com

Cloud native security, identity and access control. All things #OpenPolicyAgent. Creator of #Regal the #Rego linter. Problems architect, thought loss leader, 0.10X engineer and maintainer of two kids. Based in Stockholm πŸ‡ΈπŸ‡ͺπŸ‡ΈπŸ‡ͺ


Notes
696
Following
0
Followers
0
GitHub
https://github.com/anderseknert
OPA
https://www.openpolicyagent.org/
Regal
https://github.com/open-policy-agent/regal
Anders Eknert
@anderseknert@swecyb.com

Just realized I lost my pinned post when moving to a new instance, so here's a new one. See my profile for an #introduction to who I am β€” what I want to talk about here is the project I've been working on the most recently. That project is #Regal, a linter and a language server for #OPA's policy language #Rego.

What started out as a simple linter is now a complete companion tool for anyone working with Rego, providing developers new to the language a platform for learning, and seasoned developers means to enforce best practices and guardrails around their policies.

If you're working with anything related to OPA and Rego, try it out! If it doesn't help you in your work, that's a bug and I want to know about it. And if there's anything else related to OPA or Rego you want to ask someone about, my DMs are always open for that.

https://github.com/StyraInc/regal/


Anders Eknert
@anderseknert@swecyb.com

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!

Anders Eknert
@anderseknert@swecyb.com

Just realized I lost my pinned post when moving to a new instance, so here's a new one. See my profile for an #introduction to who I am β€” what I want to talk about here is the project I've been working on the most recently. That project is #Regal, a linter and a language server for #OPA's policy language #Rego.

What started out as a simple linter is now a complete companion tool for anyone working with Rego, providing developers new to the language a platform for learning, and seasoned developers means to enforce best practices and guardrails around their policies.

If you're working with anything related to OPA and Rego, try it out! If it doesn't help you in your work, that's a bug and I want to know about it. And if there's anything else related to OPA or Rego you want to ask someone about, my DMs are always open for that.

https://github.com/StyraInc/regal/