Repository navigation
v1.0.2
Summary
v1.0.2 improves consumer-facing deployment verification by asserting stack outputs after deployment.
What Changed
- Added post-deployment CI validation step in
Check PR:- Calls
cweb deployments describe --item-id ... - Reads
deployment.outputsfrom Management API - Fails CI if expected output values drift
- Calls
- Validated outputs include:
ApiBaseUrlOpenAPISpecEndpointStatusEndpointApiGatewayEndpoint(debug, non-empty)
Why
Management/UI consumers should focus on custom-domain endpoints, not raw execute-api URLs. This release adds an explicit automated guardrail to enforce that contract.
Validation
- PR workflow passed with output assertions enabled.
- Deployment output payload confirmed expected values for
template-api.dev.connected-web.servicesURLs.
Notes
This release is intentionally incremental on top of v1.0.1: no deployment model change, only stronger post-deploy correctness checks.