Other than that if you follow the steps in the self hosting guide you should end up with the orchestrator up and running
along with a github app successfully installed. The repo you wish to try with digger should be installed onto the orchestrator.
You will need to install digger cli onto the buildkite agent. To achieve this we can run the following
we need to download the appropriate binary from the releases: https://github.com/diggerhq/digger/releases/tag/vLatest.
For example:
You need to prepare a digger.yml to configure your terraform projects. For that refer to our quickstart
guides. For a quick one all you need would be a path to a directory and project name:
Create the buildkite pipeline associating it with your repository, give it a name and a description.
For environment variables you only need to set your digger license key: DIGGER_LICENSE_KEY=xxxyyy.
In the steps of the pipeline you just need to add a step to invoke digger as follows:
Copy
Ask AI
digger run_spec --spec "$DIGGER_SPEC"
This will instruct digger to run the “spec” which is composed and sent from the backend. That should be
all you need to set up and try digger!
In order to test your setup try to create a pull request in your repo. You should see in the backend logs
that a webhook event was received and an initial comment should be triggered in your pull request. Your
buildkite should also trigger and also perform a plan