Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve test info in README #115

Merged
merged 3 commits into from
Mar 4, 2019
Merged

improve test info in README #115

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d07b756
remove location/zone env vars. See #114
bleything Mar 2, 2019
8e7e2b7
add instructions to enable billing and services
bleything Mar 2, 2019
dab4750
be specific about which region to increase quota in
bleything Mar 2, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,15 +286,23 @@ This example assumes there are sufficient privileges to list all GCP projects.
$ gcloud config set project <project-name>
$ gcloud config list project
```
3. Ensure the `In-use IP addresses` [quota](https://console.cloud.google.com/iam-admin/quotas) is set to 20 or above
3. Enable billing for your new project
4. Enable various services necessary to run the tests:
```bash
$ gcloud services enable compute.googleapis.com \
sourcerepo.googleapis.com \
dns.googleapis.com \
container.googleapis.com \
cloudkms.googleapis.com \
cloudbuild.googleapis.com
```
5. Ensure the `In-use IP addresses` [quota](https://console.cloud.google.com/iam-admin/quotas) is set to 20 or above for `europe-west2`

4. Environment variables can be used to specify project details e.g.
6. Environment variables can be used to specify project details e.g.
```bash
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:
Expand All @@ -303,7 +311,7 @@ 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:
7. Run the integration tests via:

```bash
$ bundle install
Expand Down