Deploy and destroy CDK-managed stacks to run integration tests against real AWS.
npx skills add https://github.com/go-to-k/cdkd --skill run-integ
Please help me install this Agent Skill. Skill: run-integ Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/run-integ Command: npx skills add https://github.com/go-to-k/cdkd --skill run-integ
This Skill validates end-to-end functionality by running integration tests against a real AWS account, including deploy and destroy cycles for CDK/CDKD workflows, ensuring correctness in production-like environments.
Run integration tests against real AWS using the run-integ skill to deploy, verify, and destroy CDK stacks for a chosen test or all tests.
High-intent search queries and answers about installing and using this skill.
To run end-to-end AWS integration tests, you deploy CDK-managed stacks to a real AWS account, verify their behavior, and destroy them to ensure cleanup. This validates correctness in production-like environments using synth, deploy, verify, and destroy phases.
State management during CDK integration testing uses a dedicated state bucket in us-east-1 to manage artifacts and coordinate cleanup. This ensures clean environments by tracking deployed resources and facilitating their destruction after verification.
The AWS integration test lifecycle for cdkd includes synth, deploy with --all, verification, orphan cleanup, destroy, and ledger record. These steps validate multi-stack deployments, schema migrations, and multi-resource setups against real AWS resources.
Yes, you can validate schema migrations and multi-resource setups in AWS by deploying real CDK stacks and verifying end-to-end behavior. This testing approach supports multi-stack deployments and schema changes within a controlled AWS account.
To clean up orphaned AWS resources after destroying CDK stacks, the integration testing process includes an explicit orphan-cleanup step. This removes residual artifacts and ensures a clean environment by managing state through a designated bucket.
Yes, you need a real AWS account to verify CDK workflows end-to-end. The integration tests deploy and destroy actual CDK-managed stacks in us-east-1 to validate correctness in production-like environments rather than using mocked resources.
clawdataAutomate AWS S3 bucket listing, file transfers, and directory syncs.
JaiminVadadoriyaGenerate test reports and dashboards with Allure, Grafana, and ReportPortal.
stacksjsGuide AWS deployment for Stacks projects with CloudFormation and CDK.
kasiopeiyaAutomate local validation of AWS CDK code with linting, builds, snapshot tests, and cdk synth.
