Migrate from the localstack CLI to lstk - #28
Conversation
| # Disabled: `lstk aws`/`lstk cdk` (used via the Makefile targets that preview-cmd | ||
| # below calls) always target their own locally-managed emulator and ignore | ||
| # AWS_ENDPOINT_URL, so they can't reach the remote ephemeral instance this | ||
| # workflow provisions. Re-enable once that's resolved. |
There was a problem hiding this comment.
This is already resolved, although the lstk docs haven't been updated to reflect that AWS_ENDPOINT_URL is now recognized.
There was a problem hiding this comment.
Done — re-enabled the pull_request trigger and removed the comment block.
There was a problem hiding this comment.
Re-enabled, and lstk does reach the ephemeral instance now (all CloudFormation calls succeed). The run still fails one step later though: CDK asset publishing to S3 gets a TLS failure (write EPROTO ... tlsv1 alert internal error) — the upload uses virtual-hosted-style addressing (<bucket>.ls-xxx.sandbox.localstack.cloud), a second subdomain level the sandbox wildcard cert doesn't cover. Looks like a platform-side limitation rather than something to patch in the sample; left the trigger enabled so the behavior is visible. Happy to re-disable if the red check is too noisy until that's fixed.
|
⚡️ Running CI build with LocalStack ... |
…tive environments
2 participants
Summary
localstack/awslocal/cdklocalinvocations withlstkacross the Makefile, README, npm scripts, and CI workflows.setup-localstackaction in the main CI workflow withnpm install -g @localstack/lstk+lstk start.lstkyet (same treatment as the quiz app).tflocalinstall step; this repo has no Terraform.Testing
Part of DEVX-1056