You will need to include the license key environment variable to the backend and the cli: DIGGER_LICENSE_KEY=xxxyyy
You can ignore all the steps regarding setting up Github app and all GITHUB_** environment variables
For gitlab CI configuration you need to specify the following environment variables:
Copy
Ask AI
DIGGER_CI_BACKEND=gitlab_pipelinesDIGGER_GITLAB_WEBHOOK_SECRET=abc123DIGGER_GITLAB_ACCESS_TOKEN=glpat-xxxxyyyyyzzzzz # (this is your gitlab access token from prerequisite step)`DIGGER_GITLAB_BASE_URL=https://git.mydomain.com/api/v4
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 webhook set for your gitlab POC repo.
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:
Copy
Ask AI
projects: - name: dev dir: dev/
Setting up Gitlab webhooksIn the repo where you are interested to integrate with digger you need to set up a webhook pointing to your digger hostname. Go to Settings > Webhooks and add digger host name. Set the secret token as “abc123” (same as DIGGER_GITLAB_WEBHOOK_SECRET) above. make sure that “Comments” and “Merge request events” are selected for Trigger events. Finally you can save.
To create a Gitlab pipeline you can use a .gitlab-ci.yml file in the root of your file. In this you need to create a script which downloads Digger binary and invokes it, the purpose here is to have this pipeline triggered by Digger externally. Here is an example of such file:
In order to test your setup try to create a pull request in your repo. After you Comment “digger plan” 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 Gitlab should also trigger and also perform a plan. If successful the job will comment back the plan as follows: