decomposer: generate deliverable files for Discover and structure the solution's functional requirements, non-functional requirements, constraints, assumptions, and open questions without selecting cloud products.; Select Google Cloud products from the confirmed requirements and produce the solution architecture, Mermaid diagram, architecture description, and Terraform infrastructure-as-code.; Validate the Terraform infrastructure and architecture artifacts without deploying resources by running formatting checks, Terraform validation, and a dry-run or plan-oriented deployment check.; Package the approved requirements, architecture, Mermaid diagram, Terraform IaC, and validation results into solution-architecture-guide.md in the gcp_solution_architecture_agent repository.; Verify that the gcp_solution_architecture_agent repository contains the packaged solution-architecture-guide.md with the approved workflow outputs.; Verify that the repository is derived from the workflow_agent template and implements the complete four-phase Google Cloud solution architecture workflow alongside the packaged guide.; Publish the verified gcp_solution_architecture_agent repository with its completed workflow implementation and solution architecture guide.; Verify that the published repository revision contains the completed workflow implementation and solution architecture guide.
This commit is contained in:
27
README.md
27
README.md
@@ -1,21 +1,22 @@
|
||||
# GCP Solution Architecture Agent
|
||||
# gcp_solution_architecture_agent
|
||||
|
||||
A four-phase workflow deliverable for a resilient, event-driven Google Cloud reference architecture.
|
||||
A four-phase Google Cloud solution-architecture workflow:
|
||||
|
||||
## Workflow
|
||||
1. Discover requirements without selecting products.
|
||||
2. Select products and produce architecture artifacts.
|
||||
3. Validate Terraform and architecture artifacts without provisioning.
|
||||
4. Package and verify the guide.
|
||||
|
||||
1. **Discover** — capture functional and non-functional requirements without choosing products.
|
||||
2. **Architect** — map confirmed requirements to Google Cloud products and produce Mermaid plus Terraform.
|
||||
3. **Validate** — run formatting, Terraform validation, and a no-apply plan check.
|
||||
4. **Package** — publish the approved artifacts and verification record in `solution-architecture-guide.md`.
|
||||
The repository also includes the verification and publication contracts for manifest steps 4–7. See [`solution-architecture-guide.md`](solution-architecture-guide.md).
|
||||
|
||||
The repository is derived from the `workflow_agent` template and keeps product selection out of discovery until requirements are recorded.
|
||||
|
||||
## Local checks
|
||||
## Commands
|
||||
|
||||
```bash
|
||||
python3 -m unittest discover -s tests -v
|
||||
./scripts/validate.sh
|
||||
python -m pytest
|
||||
terraform -chdir=terraform fmt -check -recursive
|
||||
terraform -chdir=terraform init -backend=false
|
||||
terraform -chdir=terraform validate
|
||||
python scripts/validate_artifacts.py
|
||||
```
|
||||
|
||||
`validate.sh` requires Terraform 1.6.x and Google provider 6.x; it never applies resources. Set `TF_VAR_project_id` to run Terraform checks.
|
||||
The Terraform checks are intentionally plan-oriented and do not apply resources. A real plan requires Google credentials and a project ID.
|
||||
|
||||
Reference in New Issue
Block a user