Skip to content

Migrate from the localstack CLI to lstk - #6

Open
HarshCasper wants to merge 1 commit into
masterfrom
devx-1056-migrate-to-lstk
Open

Migrate from the localstack CLI to lstk#6
HarshCasper wants to merge 1 commit into
masterfrom
devx-1056-migrate-to-lstk

Conversation

@HarshCasper

Copy link
Copy Markdown
Member

Summary

  • Replace localstack/awslocal/samlocal invocations with lstk across the Makefile, README, and CI workflow.
  • Add lstk setup aws in CI since the job parses lstk aws output.

Testing

  • CI workflow run on this branch.

Part of DEVX-1056

DEBUG=1 LOCALSTACK_AUTH_TOKEN=$LOCALSTACK_AUTH_TOKEN localstack start -d
# Wait 30 seconds for the LocalStack container to become ready before timing out
LOCALSTACK_DEBUG=1 LOCALSTACK_AUTH_TOKEN=$LOCALSTACK_AUTH_TOKEN lstk start --non-interactive
# Wait for the LocalStack container to become ready before timing out

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this comment, and the echo following it are a bit misleading. I suggest we only include best practices in our sample application, because that's what humans/agents will copy.

Comment thread Makefile

## Make sure the LocalStack container is up
ready:
@echo Waiting on the LocalStack container...

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the samples that I've modified, I generally removed the ready target, since it adds no value with lstk.

Comment thread README.md
```

We specified `DEBUG=1` to get the printed LocalStack logs directly in the terminal to help us see the event-driven architecture in action. If you prefer running LocalStack in detached mode, you can add the `-d` flag to the `localstack start` command, and use Docker Desktop to view the logs.
We specified `LOCALSTACK_DEBUG=1` to get the printed LocalStack logs directly in the terminal to help us see the event-driven architecture in action. If you prefer running LocalStack in the background, you can add the `--non-interactive` flag to the `lstk start` command, and use Docker Desktop to view the logs.

@peter-smith-phd peter-smith-phd Aug 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not correct, since lstk always run in a detached mode, and not just when --non-interactive is used.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants