Files
gcp_solution_architecture_a…/requirements.yaml

32 lines
1.9 KiB
YAML

repository_name: gcp_solution_architecture_agent
template_url: https://github.com/GoogleCloudPlatform/workflow_agent
product_selection_deferred: true
functional_requirements:
- Accept authenticated HTTPS requests containing an event payload.
- Validate, durably enqueue, and asynchronously process accepted events.
- Persist raw event records for replay and audit.
- Expose an operational health endpoint and structured application logs.
- Support separate development and production environments through variables.
non_functional_requirements:
- Target at-least-once delivery with idempotent consumers.
- Provide regional high availability for managed serving and messaging components.
- Encrypt data in transit and at rest using managed encryption by default.
- Scale ingestion and processing independently based on request and backlog load.
- Retain audit data for 30 days by default and make retention configurable.
- Apply least-privilege service identities and observable failure handling.
constraints:
- Deploy only into an existing Google Cloud project supplied by the operator.
- Terraform must be planable without provisioning resources.
- No application container image is built or deployed by this repository.
- Product selection is explicitly deferred during discovery and recorded afterward.
assumptions:
- The workload is regional and an initial single-region deployment is acceptable.
- A container image is supplied by an external CI/CD pipeline.
- The runtime can use OIDC/IAM authentication and publish to messaging.
- Event consumers are idempotent and tolerate duplicate delivery.
open_questions:
- What are the peak requests per second and payload size limits?
- Which region, compliance boundary, and customer-managed key policy apply?
- What downstream systems receive processed events?
- What SLO, alert thresholds, and on-call escalation policy are required?