Introduction

GitHub Actions Integration

This is an example of Github actions that executes prancer enterprise command line for compliance tests. Based on how prancer enterprise works, you need to ensure the below conditions are met:

• Install Python in the build environment
• Install prancer-cli from PyPi
• In the step that executes the CLI, define at least these two environment variables:
  • ENTCLI_KEY
  • ENTCLI_SECRET
  • Note: Is highly recommended to define the value of the variables as Secrets

In order to create a Github Action pipeline you need to define a YAML file inside the directory github/workflows from your repository. Let's create an example.yml file on github/workflows with the below content.

name: Prancerent Test
on: push
jobs:
build:
    name: Test prancerent
    runs-on: ubuntu-latest
    steps:
    - name: Set up QEMU
        uses: docker/setup-qemu-action@v1
    - name: Set up Docker Build
        uses: docker/setup-buildx-action@v1
    - name: Set up Python 3.8
        uses: actions/setup-python@v2
        with:
        python-version: "3.8"
    - name: install prancer-cli
        run: pip install prancer-cli==1.0.6
    # You can add here a step to download your source code
    - name: prancer_test
        run:

prutil -h prutil -a create prutil -t default_container env: ENTCLI_KEY: ${{ secrets.ENTCLI_KEY }} ENTCLI_SECRET: ${{ secrets.ENTCLI_SECRET }} SERVER: ${{ secrets.SERVER }}

That's it, the pipeline should be triggered after each push to any of the branches, you can customize it according to your needs. An execution might look something like this:

You can find the complete pipeline script on our github hello world project:

prancer-hello-world/action.yaml at master · prancer-io/prancer-hello-world (github.com)