Feature Request: Implement NoVersioning for GCP buckets

[eadderley]

We're trying to use terraboard to inspect our absolutely massive state files. Unfortunately, to go along with their absolutely massive size, they're versioned going back 4 years in some cases, with near-daily versions.

This makes Terraboard tragically unusable in our case.

It'd be super cool if you all could implement NoVersioning for GCP bucket lookups. 🙂

[hbollon]

Indeed, it could be really nice to have. I will have a look

[hbollon]

I pushed a commit to support noLocks and noVersioning features with others providers than AWS, however I don't have any GCP resources to test it. Can you build an image using the integration-tests branch and give it a try please? 🙏

[eadderley]

@hbollon Amazing! Will make time for this next week.

[eadderley]

Well, my previous comment was obviously a fib. However, I managed to steal some time during this sprint to test it. It seems to be working fine! Will verify tomorrow and then have a teammate double check.

Thanks for this!

[hbollon]

Glad to hear that ! 😄
I wait your final validation to merge this 👍

[eadderley]

Well, unfortunately it doesn't seem to be loading any versions. I took a brief look at the code and suspect the offending line is this one, with the time.Now(). Not sure how AWS is handling that, maybe the API automatically pulls the nearest timestamp to it, but I don't think GCP's works the same way.

[eadderley]

Disregard, ID-10-T error. set no-sync: false and it's populating

[eadderley]

Yeah, I don't think that's done it.

log:
  level: error
  format: json

database:
  host: db
  port: 5432
  user: gorm
  password: mypassword
  name: gorm
  no-sync: false
  sslmode: disable

gcp:
  - gcs-bucket:
      - up-terraform-tfstate-aa3c
    gcp-sa-key-path: /opt/build/up-terraform-seed-9439-097878bac0b4.json
    no-versioning: true

Also tried with env var TERRABOARD_NO_VERSIONING: true in docker-compose.yml.

[eadderley]

Hmm, I'm also getting versions still in our much saner AWS env, so I'm willing to believe I'm misunderstanding or misconfiguring something here

log:
  level: error
  format: json

database:
  host: db
  port: 5432
  user: gorm
  password: mypassword
  name: gorm
  no-sync: false
  sslmode: disable

aws:
  - access-key: ####
    secret-access-key: ####
    dynamodb-table: terraboard-dynamodb
    region: us-east-1
    no-versioning: true
    s3:
      - bucket: terraform-dev
        key-prefix: uplight-inc/
        file-extension: [.tfstate]
        force-path-style: true

web:
  port: 8080

[eadderley]

2nd ID-10-T error resolved, stuck no-versioning under provider: as

provider:
    no-versioning: true

and we're off to the the races.

We're missing a few state files, but they appear to be named non-standardly named or have other issues that mean we don't actually care about them. I can provide further information if you're interested.

I think you're good to go!