Skip to content

v0.4.0 - Using the GCP Provider
Compare
Choose a tag to compare
@displague displague released this 01 Feb 15:01
v0.4.0
cbcc454
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Upgrade notes

To update from v0.3.0, create metal_ variables by renaming the old ambiguously named variables (as described below), configure the gcp_project_id variable, and run gcloud auth application-default login.

Run terraform init to fetch the GCP provider.

Changes

  • GCP Provider is now used to manage Google Cloud keys
    • gcp_project_id variable is now required
  • gcp_keys_path now defaults to "", only set this if you want to manage the keys yourself (which was the previous behavior, using utils/keys). Delete or secure these keys if you no longer need them.
  • Ambiguous Variables have been renamed with a metal_ prefix
    • auth_token is now metal_auth_token
    • project_id is now metal_project_id
    • organization_id is not metal_organization_id
    • create_project is now metal_create_project
    • project_name is now metal_project_name

Fixes

  • Hard-coded paths have been updated for use as a Terraform Module
  • apt has been replaced with apt-get to reduce noise in the log output
Assets 2
Loading