Skip to content

test(integ): sdk-ccapi-crossref failure-seeking integration test - #853

Merged
go-to-k merged 1 commit into
mainfrom
test/sdk-ccapi-crossref
Jun 14, 2026
Merged

test(integ): sdk-ccapi-crossref failure-seeking integration test#853
go-to-k merged 1 commit into
mainfrom
test/sdk-ccapi-crossref

Conversation

@go-to-k

@go-to-k go-to-k commented Jun 14, 2026

Copy link
Copy Markdown
Owner

Summary

Adds a failure-seeking integration fixture, sdk-ccapi-crossref, that
exercises the boundary between cdkd's two provisioning paths: SDK Providers
and the Cloud Control API fallback.

This is a test-only change. There are no src/** modifications.

What it covers

  • Heterogeneous routing in a single stack. The fixture deliberately mixes
    resources provisioned via SDK Providers with resources provisioned via the
    Cloud Control API fallback, so a single deploy drives both routing layers
    concurrently.
  • Bidirectional cross-references across the routing boundary. Attributes
    resolved through one routing path are threaded into resources created via the
    other, in both directions. This stresses intrinsic-function resolution
    (Ref / Fn::GetAtt) and DAG ordering across the SDK-Provider <-> Cloud
    Control API boundary, a path that narrow single-routing fixtures never
    exercise.
  • Correctness assertions in verify.sh. The post-deploy checks confirm that
    each cross-referenced attribute resolves to the value produced by the other
    routing path, and the post-destroy sweep confirms no orphan resources remain.

Validation

Validated PASS against real AWS as part of the batch-2/3 run: clean deploy
followed by a clean destroy, with no leftover AWS resources.

Notes

Coverage matrices (docs/_generated/*, docs/integ-coverage.md,
docs/scenario-coverage.md) and the scenario-coverage script were regenerated
to register the new fixture. No Closes # issue is associated with this PR.

Add a failure-seeking integration fixture exercising the boundary between
SDK Providers and the Cloud Control API. The stack mixes heterogeneously
routed resources (some provisioned via SDK Providers, some via the Cloud
Control API fallback) and wires bidirectional cross-references between
them so that attributes resolved through one routing path feed into
resources created through the other. This stresses intrinsic-function
resolution and DAG ordering across the routing boundary, a path narrow
single-routing fixtures never cover.

Test-only: no src changes. Validated PASS against real AWS via the
batch-2/3 run (clean deploy + destroy, no orphan resources).
@go-to-k
go-to-k merged commit d4c80f1 into main Jun 14, 2026
5 checks passed
@go-to-k
go-to-k deleted the test/sdk-ccapi-crossref branch June 14, 2026 02:04
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.221.10 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant