#rego — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rego, aggregated by home.social.
-
Prolog nezmizel. Jeho hlavní myšlenku dnes potkáváme v nástrojích, které se Prologu na první pohled nepodobají: v CodeQL pro analýzu kódu, v Rego pro policy-as-code, v Z3 pro práci s omezeními a v Leanu pro formální důkazy. Každý řeší jiný problém, ale všechny připomínají totéž: někdy je lepší popsat vztahy, pravidla, omezení nebo tvrzení než vrstvit další if.
https://zdrojak.cz/clanky/prolog-nezmizel-jen-dnes-zije-v-jinych-nastrojich/ -
Prolog nezmizel. Jeho hlavní myšlenku dnes potkáváme v nástrojích, které se Prologu na první pohled nepodobají: v CodeQL pro analýzu kódu, v Rego pro policy-as-code, v Z3 pro práci s omezeními a v Leanu pro formální důkazy. Každý řeší jiný problém, ale všechny připomínají totéž: někdy je lepší popsat vztahy, pravidla, omezení nebo tvrzení než vrstvit další if.
https://zdrojak.cz/clanky/prolog-nezmizel-jen-dnes-zije-v-jinych-nastrojich/ -
creates semantic nodes and clusters #ELISA #REGO multi-search-tag-explorer.headlines-world.com/advanced-sea... #MASSIMO #PESSINA headlines-world.com/advanced-sea... Do you like aéPiot semantics? Donate to the aéPiot semantic platform: www.paypal.com/donate?busin...
MultiSearch Tag Explorer -
creates semantic nodes and clusters #ELISA #REGO multi-search-tag-explorer.headlines-world.com/advanced-sea... #MASSIMO #PESSINA headlines-world.com/advanced-sea... Do you like aéPiot semantics? Donate to the aéPiot semantic platform: www.paypal.com/donate?busin...
MultiSearch Tag Explorer -
https://www.europesays.com/es/?p=488954 Andalucía y varias comunidades del PP ‘plantan’ a la ministra Rego en la Conferencia Sectorial de Infancia #Andalucía #BreakingNews #BreakingNews #comunidades #conferencia #ES #España #FeaturedNews #FeaturedNews #Headlines #Infancia #LatestNews #LatestNews #ministra #News #Noticias #NoticiasDestacadas #NoticiasDestacadas #plantan #PP #rego #sectorial #Spain #Titulares #ÚltimasNoticias #ÚltimasNoticias #varias
-
Wrote a little something about #rego, #OpenPolicyAgent's policy language and how I use it for some configuration problems: https://zerokspot.com/weblog/2026/02/21/complex-applogic-config-with-rego/ #blogged
-
Wrote a little something about #rego, #OpenPolicyAgent's policy language and how I use it for some configuration problems: https://zerokspot.com/weblog/2026/02/21/complex-applogic-config-with-rego/ #blogged
-
Wrote a little something about #rego, #OpenPolicyAgent's policy language and how I use it for some configuration problems: https://zerokspot.com/weblog/2026/02/21/complex-applogic-config-with-rego/ #blogged
-
Wrote a little something about #rego, #OpenPolicyAgent's policy language and how I use it for some configuration problems: https://zerokspot.com/weblog/2026/02/21/complex-applogic-config-with-rego/ #blogged
-
Wrote a little something about #rego, #OpenPolicyAgent's policy language and how I use it for some configuration problems: https://zerokspot.com/weblog/2026/02/21/complex-applogic-config-with-rego/ #blogged
-
https://docs.docker.com/build/policies - #Docker build policies written in #Rego validate #container build conditions and fail if not met. Just put a Dockerfile.rego next to the Dockerfile (or {filename}.rego to match Dockerfile location) and it'll pick it up. No build flags necessary.
-
https://docs.docker.com/build/policies - #Docker build policies written in #Rego validate #container build conditions and fail if not met. Just put a Dockerfile.rego next to the Dockerfile (or {filename}.rego to match Dockerfile location) and it'll pick it up. No build flags necessary.
-
https://docs.docker.com/build/policies - #Docker build policies written in #Rego validate #container build conditions and fail if not met. Just put a Dockerfile.rego next to the Dockerfile (or {filename}.rego to match Dockerfile location) and it'll pick it up. No build flags necessary.
-
https://docs.docker.com/build/policies - #Docker build policies written in #Rego validate #container build conditions and fail if not met. Just put a Dockerfile.rego next to the Dockerfile (or {filename}.rego to match Dockerfile location) and it'll pick it up. No build flags necessary.
-
https://docs.docker.com/build/policies - #Docker build policies written in #Rego validate #container build conditions and fail if not met. Just put a Dockerfile.rego next to the Dockerfile (or {filename}.rego to match Dockerfile location) and it'll pick it up. No build flags necessary.
-
https://www.europesays.com/es/364052/ ¿Quién hará de Jauregizar ante el Sporting de Portugal? #Deportes #ES #España #Football #Fútbol #jauregizar #rego #Soccer #Spain #SportingDePortugal #Sports #sustituto #UnaiGómez #vesga
-
Found while moving! Styra used to make a unique t-shirt for every #Kubecon back in the days. This was the first one made in the pandemic. Rudolph should have worn a mask though!
-
Found while moving! Styra used to make a unique t-shirt for every #Kubecon back in the days. This was the first one made in the pandemic. Rudolph should have worn a mask though!
-
Found while moving! Styra used to make a unique t-shirt for every #Kubecon back in the days. This was the first one made in the pandemic. Rudolph should have worn a mask though!
-
Found while moving! Styra used to make a unique t-shirt for every #Kubecon back in the days. This was the first one made in the pandemic. Rudolph should have worn a mask though!
-
Found while moving! Styra used to make a unique t-shirt for every #Kubecon back in the days. This was the first one made in the pandemic. Rudolph should have worn a mask though!
-
I love spacelift.io for a number of reasons, namely it saves you from running #Terraform or #OpenTofu in whatever "CI" tool your company uses this week (been there, hated it) and doesn't cost an arm, leg and kidney that Terraform Cloud charge you (loved TFC until that switcharoo).
Anyway, I've been wrapping up a thing I've been working on. Many SaaS tools allow you to send #webhooks, but rarely give you control over if, where and what is sent. Now #Spacelift let you control all of this using a Policy based on #OpenPolicyAgent.
SL provide an event, you develop your policy in the #Rego language, not only can you use that policy to decide: Is this an event I want to send a webhook for? But more than that, you can use the policy language to craft the exact payload. Since you may not get a choice of what that looks like on the other end.
Docs: https://docs.spacelift.io/concepts/policy/notification-policy
Now that's just for notifications etc. You can control almost anything within the tool: Logins, Plans, Triggers, Pushes and more.
-
I love spacelift.io for a number of reasons, namely it saves you from running #Terraform or #OpenTofu in whatever "CI" tool your company uses this week (been there, hated it) and doesn't cost an arm, leg and kidney that Terraform Cloud charge you (loved TFC until that switcharoo).
Anyway, I've been wrapping up a thing I've been working on. Many SaaS tools allow you to send #webhooks, but rarely give you control over if, where and what is sent. Now #Spacelift let you control all of this using a Policy based on #OpenPolicyAgent.
SL provide an event, you develop your policy in the #Rego language, not only can you use that policy to decide: Is this an event I want to send a webhook for? But more than that, you can use the policy language to craft the exact payload. Since you may not get a choice of what that looks like on the other end.
Docs: https://docs.spacelift.io/concepts/policy/notification-policy
Now that's just for notifications etc. You can control almost anything within the tool: Logins, Plans, Triggers, Pushes and more.
-
I love spacelift.io for a number of reasons, namely it saves you from running #Terraform or #OpenTofu in whatever "CI" tool your company uses this week (been there, hated it) and doesn't cost an arm, leg and kidney that Terraform Cloud charge you (loved TFC until that switcharoo).
Anyway, I've been wrapping up a thing I've been working on. Many SaaS tools allow you to send #webhooks, but rarely give you control over if, where and what is sent. Now #Spacelift let you control all of this using a Policy based on #OpenPolicyAgent.
SL provide an event, you develop your policy in the #Rego language, not only can you use that policy to decide: Is this an event I want to send a webhook for? But more than that, you can use the policy language to craft the exact payload. Since you may not get a choice of what that looks like on the other end.
Docs: https://docs.spacelift.io/concepts/policy/notification-policy
Now that's just for notifications etc. You can control almost anything within the tool: Logins, Plans, Triggers, Pushes and more.
-
I love spacelift.io for a number of reasons, namely it saves you from running #Terraform or #OpenTofu in whatever "CI" tool your company uses this week (been there, hated it) and doesn't cost an arm, leg and kidney that Terraform Cloud charge you (loved TFC until that switcharoo).
Anyway, I've been wrapping up a thing I've been working on. Many SaaS tools allow you to send #webhooks, but rarely give you control over if, where and what is sent. Now #Spacelift let you control all of this using a Policy based on #OpenPolicyAgent.
SL provide an event, you develop your policy in the #Rego language, not only can you use that policy to decide: Is this an event I want to send a webhook for? But more than that, you can use the policy language to craft the exact payload. Since you may not get a choice of what that looks like on the other end.
Docs: https://docs.spacelift.io/concepts/policy/notification-policy
Now that's just for notifications etc. You can control almost anything within the tool: Logins, Plans, Triggers, Pushes and more.
-
I love spacelift.io for a number of reasons, namely it saves you from running #Terraform or #OpenTofu in whatever "CI" tool your company uses this week (been there, hated it) and doesn't cost an arm, leg and kidney that Terraform Cloud charge you (loved TFC until that switcharoo).
Anyway, I've been wrapping up a thing I've been working on. Many SaaS tools allow you to send #webhooks, but rarely give you control over if, where and what is sent. Now #Spacelift let you control all of this using a Policy based on #OpenPolicyAgent.
SL provide an event, you develop your policy in the #Rego language, not only can you use that policy to decide: Is this an event I want to send a webhook for? But more than that, you can use the policy language to craft the exact payload. Since you may not get a choice of what that looks like on the other end.
Docs: https://docs.spacelift.io/concepts/policy/notification-policy
Now that's just for notifications etc. You can control almost anything within the tool: Logins, Plans, Triggers, Pushes and more.
-
Using or trialling OPA? We want to hear from you in our 2025 Community Survey.
https://www.surveymonkey.com/r/SCBSDZN
Whether you're new to OPA or have been on the Rego train for years, hearing about how you use OPA projects will help us share OPA for the months and years to come.
We're going to be at KubeCon tomorrow in the project pavilion. Come and say hi!
-
Using or trialling OPA? We want to hear from you in our 2025 Community Survey.
https://www.surveymonkey.com/r/SCBSDZN
Whether you're new to OPA or have been on the Rego train for years, hearing about how you use OPA projects will help us share OPA for the months and years to come.
We're going to be at KubeCon tomorrow in the project pavilion. Come and say hi!
-
Using or trialling OPA? We want to hear from you in our 2025 Community Survey.
https://www.surveymonkey.com/r/SCBSDZN
Whether you're new to OPA or have been on the Rego train for years, hearing about how you use OPA projects will help us share OPA for the months and years to come.
We're going to be at KubeCon tomorrow in the project pavilion. Come and say hi!
-
Политики над конфигами (OPA/Rego) в GitOps-пайплайне
Привет, Хабр! Представим, что вы отвечаете за десятки конфигурационных файлов Kubernetes (или Terraform, Ansible, не суть важно) в репозитории, и каждый pull request может потенциально привести к тому, что в кластер уйдёт что-то не то. Наш любимый коллега случайно поставил контейнер с privileged -правами, другой задеплоил образ из публичного репозитория Docker Hub, а третий вовсе забыл про лимиты памяти и CPU. Без автоматического контроля такие промахи легко попадут в продакшн. Ошибки в настройках сегодня одна из главных причин инцидентов безопасности в облачных средах. Как же нам держать всё под контролем? Внедрить политики как код: формализованные правила, проверяемые автоматически на каждом шаге. В этой статье я расскажу, как применять Open Policy Agent и язык Rego, чтобы навести порядок в GitOps-пайплайне и не допускать лишнего в конфигурациях. Читать про внедрение политик в GitOps
https://habr.com/ru/companies/otus/articles/960368/
#gitops #Open_Policy_Agent #Rego #Policy_as_Code #политики_как_код
-
Политики над конфигами (OPA/Rego) в GitOps-пайплайне
Привет, Хабр! Представим, что вы отвечаете за десятки конфигурационных файлов Kubernetes (или Terraform, Ansible, не суть важно) в репозитории, и каждый pull request может потенциально привести к тому, что в кластер уйдёт что-то не то. Наш любимый коллега случайно поставил контейнер с privileged -правами, другой задеплоил образ из публичного репозитория Docker Hub, а третий вовсе забыл про лимиты памяти и CPU. Без автоматического контроля такие промахи легко попадут в продакшн. Ошибки в настройках сегодня одна из главных причин инцидентов безопасности в облачных средах. Как же нам держать всё под контролем? Внедрить политики как код: формализованные правила, проверяемые автоматически на каждом шаге. В этой статье я расскажу, как применять Open Policy Agent и язык Rego, чтобы навести порядок в GitOps-пайплайне и не допускать лишнего в конфигурациях. Читать про внедрение политик в GitOps
https://habr.com/ru/companies/otus/articles/960368/
#gitops #Open_Policy_Agent #Rego #Policy_as_Code #политики_как_код
-
Политики над конфигами (OPA/Rego) в GitOps-пайплайне
Привет, Хабр! Представим, что вы отвечаете за десятки конфигурационных файлов Kubernetes (или Terraform, Ansible, не суть важно) в репозитории, и каждый pull request может потенциально привести к тому, что в кластер уйдёт что-то не то. Наш любимый коллега случайно поставил контейнер с privileged -правами, другой задеплоил образ из публичного репозитория Docker Hub, а третий вовсе забыл про лимиты памяти и CPU. Без автоматического контроля такие промахи легко попадут в продакшн. Ошибки в настройках сегодня одна из главных причин инцидентов безопасности в облачных средах. Как же нам держать всё под контролем? Внедрить политики как код: формализованные правила, проверяемые автоматически на каждом шаге. В этой статье я расскажу, как применять Open Policy Agent и язык Rego, чтобы навести порядок в GitOps-пайплайне и не допускать лишнего в конфигурациях. Читать про внедрение политик в GitOps
https://habr.com/ru/companies/otus/articles/960368/
#gitops #Open_Policy_Agent #Rego #Policy_as_Code #политики_как_код
-
Политики над конфигами (OPA/Rego) в GitOps-пайплайне
Привет, Хабр! Представим, что вы отвечаете за десятки конфигурационных файлов Kubernetes (или Terraform, Ansible, не суть важно) в репозитории, и каждый pull request может потенциально привести к тому, что в кластер уйдёт что-то не то. Наш любимый коллега случайно поставил контейнер с privileged -правами, другой задеплоил образ из публичного репозитория Docker Hub, а третий вовсе забыл про лимиты памяти и CPU. Без автоматического контроля такие промахи легко попадут в продакшн. Ошибки в настройках сегодня одна из главных причин инцидентов безопасности в облачных средах. Как же нам держать всё под контролем? Внедрить политики как код: формализованные правила, проверяемые автоматически на каждом шаге. В этой статье я расскажу, как применять Open Policy Agent и язык Rego, чтобы навести порядок в GitOps-пайплайне и не допускать лишнего в конфигурациях. Читать про внедрение политик в GitOps
https://habr.com/ru/companies/otus/articles/960368/
#gitops #Open_Policy_Agent #Rego #Policy_as_Code #политики_как_код
-
Took a walk with Harry today, and we spotted a car evidently owned by a person of culture.
-
Took a walk with Harry today, and we spotted a car evidently owned by a person of culture.
-
Took a walk with Harry today, and we spotted a car evidently owned by a person of culture.
-
Took a walk with Harry today, and we spotted a car evidently owned by a person of culture.
-
Took a walk with Harry today, and we spotted a car evidently owned by a person of culture.
-
On my way to present on #OPA and #Rego for the #CloudNative #Mauritius community. Sadly not in person ☀️ but virtually from cloudy Stockholm. Still, looking forward to getting to do some live coding!
-
On my way to present on #OPA and #Rego for the #CloudNative #Mauritius community. Sadly not in person ☀️ but virtually from cloudy Stockholm. Still, looking forward to getting to do some live coding!
-
On my way to present on #OPA and #Rego for the #CloudNative #Mauritius community. Sadly not in person ☀️ but virtually from cloudy Stockholm. Still, looking forward to getting to do some live coding!
-
On my way to present on #OPA and #Rego for the #CloudNative #Mauritius community. Sadly not in person ☀️ but virtually from cloudy Stockholm. Still, looking forward to getting to do some live coding!
-
On my way to present on #OPA and #Rego for the #CloudNative #Mauritius community. Sadly not in person ☀️ but virtually from cloudy Stockholm. Still, looking forward to getting to do some live coding!
-
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!
-
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!
-
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!
-
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!
-
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!
