{# Step 2 — pick the audit target. Project dropdown comes from gcp_projects_for_picker(); region is free text with a list of common BigQuery locations. POST runs the ADC probe again (now that we have a project to probe against) and writes ~/.governor-audit/config.json. #} {% extends "setup/layout.html" %} {% block content %}

Step 2 · Choose audit target

Pick the BigQuery project you want to audit, the region its dataset lives in, and the lookback window for the first scan. Project and region are required — everything in audit is scoped to a single (project, region) pair. Submitting this form saves the config and starts the scan in the background; you'll land on the configurations page where it continues running.

{% if errors and errors.get('_general') %}
{{ errors['_general'] }}
{% endif %} {% if discovery_error %}
{{ discovery_error }}
{% endif %}
{% if gcp_projects %} {% for project in gcp_projects %} {% endfor %} {% endif %} {% if errors and errors.get('gcp_project_id') %}

{{ errors['gcp_project_id'] }}

{% endif %}

Single-region (us-east1) or multi-region (us / eu). Must match the dataset's location.

{% if errors and errors.get('bigquery_region') %}

{{ errors['bigquery_region'] }}

{% endif %}

How far back the first scan looks at INFORMATION_SCHEMA.JOBS_BY_PROJECT. Shorter windows finish in seconds; you can re-scan with a wider window any time from the configurations page.

{% if errors and errors.get('lookback_days') %}

{{ errors['lookback_days'] }}

{% endif %}
Back
{% endblock %}