Skip to main content

How to run OPA in Docker

From the introduction of the openpolicyagent.org site:
OPA generates policy decisions by evaluating the query input against policies and data.
In this post i am going to show you an easy and fast way to test your policies by running OPA in Docker.

First, make sure you have already installed Docker and have it running:
docker ps

Inside your choosen directory, create two files. One called input.json file for your system representation and one file called example.rego for your rego policy rules.

Add the following content to your json file:

Add the following content for the example.rego:

Each violation block represents the rule that you want to validate your system against. The first violation block checks if any of the system servers have the http protocol in it. If that is the case, the server id is added to the array. In the same way, the second violation block checks for the servers that have the telnet protocol in it and if it finds a match the server id is also added to the violation array.

The final result bring all server ids that have violated any policy rule. In this way, allow is only going to be true if the number of violations are equal to zero.
count(violation) == 0 

Looking to our json file we can see that we have two servers violating our policy with the http and telnet protocols, the ci and busybox servers. So, lets run OPA in docker to find out if that is the case.

As we know we can use the opa eval command to evaluate Rego policies. So lets find out how we can run it from docker. To get docker run the eval command we must supply the input and policy files as arguments to docker using the -i and -d flags:

Run the following command, from the same directory where you saved your json and rego files, to download the opa image from docker and run it at the same time:
docker run -v $PWD:/example openpolicyagent/opa eval -i example/input.json -d example/example.rego "data.example.violation[x]"

By mapping the files of your currently directory to the example directory inside docker we can then pass those files as arguments from the comamnd line using docker.

You should get the following result from running the opa eval command:

Comments

Popular posts from this blog

Understanding RabbitMQ

Introduction RabbitMQ is a centralized message broker based on the AMQP (Advanced Message Queuing Protocol) protocol, acting as a Middleware between Producers and Consumers of different systems. In a message system, Publishers sends a message to a message broker where messages are consumed some time later by one or more Subscribers. By introducing a message brokeer between systems we are decoupling the sender application from the receiver. In this case the service that is responsible for sending or publishing the message does not need to know about any other service. All it needs to care about is the message and its format. With a message system you send a message to a message broker first and when the consumers or listeners of it become online they can start consuming from the message queue. This means you can keep sending messages without even care if the other application is online or if they had any failures. RabbitMQ Architecture Exchange, queue and bindings are the ...

A Retrospective board to call your own made with React, GraphQL and MongoDB

Introduction I have been working in a project to enable anyone to fork and run a retrospective board in its own server. I have created 2 (two) projects: one for the UI with React and GraphQL using Apollo client and one for the GraphQL server also using Apollo (Server) and MongoDB for the database. In the following sections I am going to walk you through the steps and explain how to run both projects. Main features The board main features: - History of your past iteractions saved in the Mongo database - Easy url link format to quick access any past iteractions - Automatically add action items as last action items in the new board - Quick move items to Action Items Coming next You can fork the React UI from the following GitHub repo: - Support for multiple teams - Authentication - Subscriptions (pub/sub) Code Repo You can fork the React UI from the following GitHub repo: React Retrospective UI You can fork the GraphQL Server from the following GitHub rep...

Simple, quick and easy steps to run an Oracle Database in your development environment using Docker without overloading your machine

Introduction In our development environment, besides being easy and fast to use, above all, we need a lightweight version of it to run locally, right? I have tested different Oracle images and this was the option that best work for me. In this post i will show you how you can run the Oracle Database Express Edition version on your local machine quickly and easily and also how to connect to it using Oracle SQL Developer IDE and SQL*Plus. How to do it Basically we just need two simple steps to get our Oracle database running on our local environment. First we need to login to the Oracle Container Registry so we can pull the image from it and then we just need to run it in a container. You can find more information by going to the Oracle Container Registry , under the "Browse Containers", click into Database and next click in the express Repository for the Oracle Database Express Edition. I am going to skip the docker pull step, because docker run will do it for us ...