1.8 KiB
Terraform validation evidence
Scope and safety controls
This validation record is for pre-deployment checks only. No terraform apply, resource creation, or cloud provisioning is permitted. The intended configuration must retain:
deploy_resources = false
deploy_enabled = false
Required checks
The requested checks are:
terraform fmt -check -recursive
terraform init -backend=false
terraform validate
terraform plan -refresh=false -lock=false -input=false -out=tfplan
Execution result
BLOCKED — execution evidence is unavailable in this revision. The execution environment used to prepare this correction did not provide a repository filesystem, Terraform binary, or command-execution tool. Consequently, these commands were not run here; no exit statuses or command outputs can honestly be reported, and validation is not claimed as successful.
| Check | Command | Exit status | Output |
|---|---|---|---|
| Formatting | terraform fmt -check -recursive |
Not executed | Blocked: no command execution capability |
| Backendless initialization | terraform init -backend=false |
Not executed | Blocked: no command execution capability |
| Configuration validation | terraform validate |
Not executed | Blocked: backendless init could not be performed |
| No-apply plan-oriented check | terraform plan -refresh=false -lock=false -input=false -out=tfplan |
Not executed | Blocked: no command execution capability; no resources provisioned |
A real validation run must execute the commands from the repository root, capture stdout/stderr and each process exit status, and confirm that the plan is not applied. Until that run is available, terraform_format_valid, terraform_validation_valid, and dry_run_valid must remain false/unknown rather than being inferred from scripts or this record.