Store plans in a Bucket

Github

Digger can use Github Artifacts to store terraform plan outputs. In order to enable it you can set the following argument in digger_workflow.yml:

upload-plan-destination: github

GCP

You can also configure plan outputs to be uploaded to GCP Buckets instead. This is handy in case you want your plan outputs to stay within your organisation’s approved storage providers for security or compliance reasons.

To change digger to upload the plan to GCP set the follow argument in the digger_workflow.yml file

with:
    google-lock-bucket: 'gcp'
    upload-plan-destination-gcp-bucket: 'terraform-plan-output-1239123'

AWS

You can also use AWS S3 buckets to store plan outputs.

To change digger to upload the plan to AWS S3 set the following arguments in the digger_workflow.yaml

with:
    upload-plan-destination: 'aws'
    upload-plan-destination-s3-bucket: 'terraform-plan-output-1239123'

Azure

You can also use Azure storage accounts to store plan outputs.

To change digger to upload the plan to Azure storage account set the following arguments in the digger_workflow.yaml

with:
    upload-plan-destination: 'azure'
    upload-plan-destination-azure-storage-account: 'account_name'
    upload-plan-destination-azure-container: 'container_name'