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

How to use Splunk SPL commands to write better queries - Part I

Introduction As a software engineer, we are quite used to deal with logs in our daily lives, but in addition to ensuring that the necessary logs are being sent by the application itself or through a service mesh, we often have to go a little further and interact with some log tool to extract more meaningful data. This post is inspired by a problem I had to solve for a client who uses Splunk as their main data analysis tool and this is the first in a series of articles where we will delve deeper and learn how to use different Splunk commands. Running Splunk with Docker To run Splunk with docker, just run the following command: docker run -d —rm -p 8000:8000 -e SPLUNK_START_ARGS=--accept-license -e SPLUNK_PASSWORD=SOME_PASSWORD --name splunk splunk/splunk:latest Sample Data We are going to use the sample data provided by Splunk. You can find more information and download the zip file from their web site . How does it work? In order to be able to interact with Splunk t

How to become a Blockchain developer and write your first Smart Contract

Introduction This is an introductory article to help you understanding the tools and frameworks needed so that you can know from where and how to start creating your own Smart Contracts. In this post I will give you an overview of the tools, frameworks, libraries and languages used to create a Smart Contract in the Ethereum Blockchain . In the second part of this article, we are going to see how to create a Smart Contracts using Solidity and ee are also going to see how to run a Blockchain locally using Ganache , so that you can deploy, interact and test your Smart Contract in your local development environment. According to a definition from the Wikipedia website: A blockchain is a decentralized, distributed, and often public, digital ledger consisting of records called blocks that are used to record transactions across many computers so that any involved block cannot be altered retroactively, without the alteration of all subsequent blocks.. What do you need to know? T