boltops-tools / terraspace_plugin_google Goto Github PK

I may be mistaken, but it seems this plugin does not allow the usage of GOOGLE_CREDENTIALS / GOOGLE_BACKEND_CREDENTIALS which is very confusing when the gcs remote state supports loading the service account key from these env vars.

I ran into this issue when trying to migrate our terraform CI to use terraspace instead as we have both of the above env vars defined.

GOOGLE_BACKEND_CREDENTIALS should be used first as the bucket could be in a different project from the GCP resources being deployed.

I'm seeing this with terraspace version 0.6.13 & ruby 2.7.0

When a new GCS backend bucket is created it defaults to the US multi-region. This behaviour should be configurable so that the backend state bucket can be created in a desired location.

Perhaps needs changes to support the config in :

• https://github.com/boltops-tools/terraspace_plugin_google/blob/master/lib/terraspace_plugin_google/interfaces/config.rb

and the implementation changes in

• terraspace_plugin_google/lib/terraspace_plugin_google/interfaces/backend.rb

  Line 22 in cace2a1

  def create_bucket(bucket)