Description of Documentation Need
The DDG has the following refence is phase 0 for the terraform.tfvars.sample:
locations for GCS, BigQuery, and logging buckets created here
locations = {
bq = "<region>"
gcs = "<region>"
logging = "<region>"
pubsub = ["<region>"]
kms = "<region>"
}
However, the actual code in the fast/stages-aw/0-bootstrap/terraform.tfvars.sample has:
region configuration - this will automatically populate locations for GCS, BigQuery, KMS, and logging buckets
Default to us-east4 for IL5/FedRAMP compliance - adjust as needed
regions = {
primary = "us-east4" # Change to your preferred region - this will be used for all bootstrap resources
}
I'm sure there are probably other configuration drifts that may have occurred since the May 11 2026 v 2.9.1 version based on other commits that require changes to the DDG to keep it in sync with changes to the code so that it stays authoritative for the configuration and deployment process.
Target Audience
Operators
Proposed Location
In the existing DDG
Content Outline / Draft
Fix the error outlined above. If there is any other drift, resolve that as well. Ideally, the process of making any change to the code would validate if any changes are needed in the DDG and then both get committed together and the version and date should be updated with each PR.
Compliance Context (if applicable)
N/A
Description of Documentation Need
The DDG has the following refence is phase 0 for the terraform.tfvars.sample:
locations for GCS, BigQuery, and logging buckets created here
locations = {
bq = "
<region>"gcs = "
<region>"logging = "
<region>"pubsub = ["
<region>"]kms = "
<region>"}
However, the actual code in the fast/stages-aw/0-bootstrap/terraform.tfvars.sample has:
region configuration - this will automatically populate locations for GCS, BigQuery, KMS, and logging buckets
Default to us-east4 for IL5/FedRAMP compliance - adjust as needed
regions = {
primary = "us-east4" # Change to your preferred region - this will be used for all bootstrap resources
}
I'm sure there are probably other configuration drifts that may have occurred since the May 11 2026 v 2.9.1 version based on other commits that require changes to the DDG to keep it in sync with changes to the code so that it stays authoritative for the configuration and deployment process.
Target Audience
Operators
Proposed Location
In the existing DDG
Content Outline / Draft
Fix the error outlined above. If there is any other drift, resolve that as well. Ideally, the process of making any change to the code would validate if any changes are needed in the DDG and then both get committed together and the version and date should be updated with each PR.
Compliance Context (if applicable)
N/A