Terraform State Backend

[cdenneen]

How can you set the terraform backend in pecdm?

Something like:

#! /bin/bash
PROJECT_ID="YOUR_PROJECT_ID" \
TF_USERNAME=${TF_USERNAME} \
TF_PASSWORD=${TF_PASSWORD} \
TF_ADDRESS="https://YOUR_GitLab_Domain/api/v4/projects/YOUR_PROJECT_ID/terraform/state/YOUR_State_File" \

terraform init \
  -backend-config=address=${TF_ADDRESS} \
  -backend-config=lock_address=${TF_ADDRESS}/lock \
  -backend-config=unlock_address=${TF_ADDRESS}/lock \
  -backend-config=username=${TF_USERNAME} \
  -backend-config=password=${TF_PASSWORD} \
  -backend-config=lock_method=POST \
  -backend-config=unlock_method=DELETE \
  -backend-config=retry_wait_min=5

Would be useful for CI/CD to run pecdm where the state can be stored.

This is just an example of a terraform http backend using GitLab but it could be any supported backend.

[ody]

We currently have no capability to leverage remote state in pecdm because of limitations in the terraform::initialize task. A feature request to add it to that module needs to precede anything prior to us enabling it in pecdm.

[davidsandilands]

@cdenneen could you raise a feature request to https://git@github.com/puppetlabs/puppetlabs-terraform/issues I did speak to the internal Puppet team who said they would be happy to review contributions to this module but development would need to be lead by community

[davidsandilands]

@cdenneen on discussion the @puppetlabs/solutions-architecture team has decided to implement this and will raise a feature request and develop this capability on the terraform module