-
Notifications
You must be signed in to change notification settings - Fork 37
Mention the lstk CLI in the localstack CLI docs #700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,8 +18,7 @@ It provides a built-in terminal UI (TUI) for interactive use and plain text outp | |
| Running `lstk` with no arguments takes you through the entire flow automatically. | ||
|
|
||
| :::note | ||
| `lstk` is in early release and does not yet support advanced features like **Cloud Pods**, **Extensions**, and **Ephemeral Instances**. For these features, use the [LocalStack CLI](/aws/tooling/localstack-cli/). | ||
| Both tools can be installed and used on the same machine. | ||
| `lstk` covers the everyday emulator workflow: lifecycle (`start`, `stop`), monitoring (`status`, `logs`), storage (`snapshot`), and more. | ||
| ::: | ||
|
|
||
| ## Prerequisites | ||
|
|
@@ -458,11 +457,11 @@ Restart your shell after persisting completions. | |
|
|
||
| ### What is the difference between `lstk` and the `localstack` CLI? | ||
|
|
||
| Both tools can start, stop, and manage the LocalStack emulator. | ||
| `lstk` is a newer CLI built in Go with a TUI, while the `localstack` CLI is the established Python-based tool with support for Cloud Pods, Extensions, Ephemeral Instances, and other advanced features. | ||
| Both tools can start, stop, and manage the LocalStack emulator, and both work with Cloud Pods — `lstk` via its `snapshot` command and the [`localstack` CLI](/aws/tooling/localstack-cli/) via its `pod` command. | ||
| `lstk` is a newer CLI built in Go with a TUI; the `localstack` CLI is the established Python-based tool that additionally supports Extensions, Ephemeral Instances, and other advanced features `lstk` doesn't cover yet. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @gtsiolis considering that we will deprecate When we deprecate
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You're right, probably not worth highlighting. For context, the goal was to make I will remove ephemeral instances and extensions mention next week, but you are also welcome to take this over and push any changes or merge before that. |
||
|
|
||
| Both can be installed side by side. | ||
| Use `lstk` for fast daily start/stop workflows and `localstack` for advanced platform features. | ||
| Use `lstk` for fast daily workflows and the `localstack` CLI when you need its additional platform features. | ||
|
|
||
| ### Can I use `lstk` with Docker Compose? | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @gtsiolis, we don't want to have a mention of the soon to be deprecated localstack cli in the lstk doc. We should keep this doc only focused on lstk.
And since we're fully deprecating the LS cli, to me this is another reason we don't need this section moving fwd :)