This InSpec resource pack uses the native Google Cloud Platform (GCP) support in InSpec and provides the required resources to write tests for GCP.

This implementation was inspired on the ideas by Martez Reed.

1. Install and configure the Google cloud SDK

Download the SDK and run the installation:

./google-cloud-sdk/install.sh

2. Create credentials file via:

$ gcloud auth application-default login

If successful, this should be similar to:

$ cat ~/.config/gcloud/application_default_credentials.json 
{
  "client_id": "764086051850-6qr4p6gpi6hn50asdr.apps.googleusercontent.com",
  "client_secret": "d-fasdfasdfasdfaweroi23jknrmfs;f8sh",
  "refresh_token": "1/asdfjlklwna;ldkna'dfmk-lCkju3-yQmjr20xVZonrfkE48L",
  "type": "authorized_user"
}

3. Enable the appropriate APIs that you want to use:

• Enable Compute Engine API
• Enable Kubernetes Engine API

1. Create a new GCP project
2. Ensure this is currently set following: https://cloud.google.com/shell/docs/examples

$ gcloud config set project <project-name>
$ gcloud config list project

3. Ensure the In-use IP addresses quota is set to 20 or above

4. Environment variables can be used to specify project details e.g.

export GCP_PROJECT_NAME=<project-name>
export GCP_PROJECT_NUMBER=<project-number>
export GCP_PROJECT_ID=<project-id>
export GCP_LOCATION=<region, defaults to europe-west2>
export GCP_ZONE=<zone, defaults to europe-west2-a>

Some resources require elevated privileges to create in GCP. These are disabled by default but can be activated via:

export GCP_ENABLE_PRIVILEGED_RESOURCES=1

This takes effect during the "plan" task as described in the next section. Affected terraform resources are included/excluded and associated inspec tests enabled/disabled accordingly.

4. Run the integration tests via:

$ bundle install
$ bundle exec rake test:integration

Alternatively, finer grained rake tasks are also available. Executing these in order is the same as the above command:

• Initialize local workspace (terraform init)

$ bundle exec rake test:init_workspace 

• Plan integration tests - ensures variables are set for Inspec and Terraform, runs "terraform plan"

$ bundle exec rake test:plan_integration_tests 

• Set up integration tests - actually creates the resources in GCP (terraform apply)

$ bundle exec rake test:setup_integration_tests 

• Run integration tests - runs the tests (inspec exec)

$ bundle exec rake test:run_integration_tests 

• Clean up integration tests - removes GCP resources (terraform destroy)

$ bundle exec rake test:cleanup_integration_tests 

InSpec relies on the GCP API's to verify the settings. Therefore, it requires access to the API. If you try to access an API via an InSpec resource that is not enabled in your account, then you see an error like:

googleapi: Error 403: Access Not Configured. Compute Engine API has not been used in project 41111111111 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/compute.googleapis.com/overview then retry.

The terraform templates generate sufficient resources to require an increase to default in_use IP addresses. Normally new projects have 10, increasing this to 20 or higher should be sufficient.

To find this setting, log in to the GCP web interface and go to IAM and admin->Quotas and look for "Compute Engine API In-use IP addresses". From here you can "Edit quotas" to request more.

Changed Quota:
+----------------------+------------------+
| Region: europe-west2 | IN_USE_ADDRESSES |
+----------------------+------------------+
|       Changes        |     8 -> 64      |
+----------------------+------------------+

Sometimes there can be occasional errors when performing the cleanup rake task. This happens when resources are already deleted and can be ignored.

The InSpec GCP resources are community supported. For bugs and features, please open a github issue and label it appropriately.

This implementation is inspired by inspec-azure and inspec-gcp