45 lines
1.2 KiB
Markdown
Executable File
45 lines
1.2 KiB
Markdown
Executable File
# Validation
|
|
|
|
## Local Validation
|
|
|
|
On some Windows desktops, direct `.ps1` execution may be blocked by execution policy. Use:
|
|
|
|
```powershell
|
|
powershell -ExecutionPolicy Bypass -File .\scripts\bootstrap.ps1
|
|
powershell -ExecutionPolicy Bypass -File .\scripts\validate-terraform.ps1
|
|
```
|
|
|
|
## Terraform Validation
|
|
|
|
The validation script runs:
|
|
|
|
```bash
|
|
terraform fmt -recursive -check
|
|
terraform init -backend=false
|
|
terraform validate
|
|
```
|
|
|
|
After filling `terraform.tfvars`, run:
|
|
|
|
```bash
|
|
cd terraform/envs/demo
|
|
terraform init
|
|
terraform plan -out tfplan
|
|
terraform apply tfplan
|
|
```
|
|
|
|
## Scenario Validation
|
|
|
|
For each scenario:
|
|
|
|
1. Run `sql/99_reset.sql`.
|
|
2. Run `00_schema.sql`, `01_seed_data.sql`, `02_identities.sql`, and `03_data_grants.sql`.
|
|
3. Connect as each persona or propagate the context through the application.
|
|
4. Run `04_test_queries.sql` or the scenario-specific activity script.
|
|
5. Compare the result with `evidence/expected-results.md`.
|
|
|
|
## Static Validation Limits
|
|
|
|
`terraform validate` checks syntax and provider schema. It does not guarantee regional database version availability, shape availability, quota, IAM policies, or service limits. Those are validated during `terraform plan` and `terraform apply`.
|
|
|