stackablectl demo

Interact with demos, which are end-to-end usage demonstrations of the Stackable data platform Usage: stackablectl demo [OPTIONS] <COMMAND> Commands: list List available demos describe Print out detailed demo information install Install a specific demo help Print this message or the help of the given subcommand(s) Options: -l, --log-level <LOG_LEVEL> Log level this application uses --no-cache Do not cache the remote (default) demo, stack and release files Cached files are saved at '$XDG_CACHE_HOME/stackablectl', which is usually '$HOME/.cache/stackablectl' when not explicitly set. --offline Do not request any remote files via the network -h, --help Print help (see a summary with '-h') -V, --version Print version File options: -d, --demo-file <DEMO_FILE> Provide one or more additional (custom) demo file(s) Demos are loaded in the following order: Remote (default) demo file, custom demo files provided via the 'STACKABLE_DEMO_FILES' environment variable, and lastly demo files provided via the '-d/--demo-file' argument(s). If there are demos with the same name, the last demo definition will be used. Use "stackablectl [OPTIONS] <COMMAND> -d path/to/demos1.yaml -d path/to/demos2.yaml" to provide multiple additional demo files. -s, --stack-file <STACK_FILE> Provide one or more additional (custom) stack file(s) Stacks are loaded in the following order: Remote (default) stack file, custom stack files provided via the 'STACKABLE_STACK_FILES' environment variable, and lastly demo files provided via the '-s/--stack-file' argument(s). If there are stacks with the same name, the last stack definition will be used. Use "stackablectl [OPTIONS] <COMMAND> -s path/to/stacks1.yaml -s path/to/stacks2.yaml" to provide multiple additional stack files. -r, --release-file <RELEASE_FILE> Provide one or more additional (custom) release file(s) Releases are loaded in the following order: Remote (default) release file, custom release files provided via the 'STACKABLE_RELEASE_FILES' environment variable, and lastly release files provided via the '-r/--release-file' argument(s). If there are releases with the same name, the last release definition will be used. Use "stackablectl [OPTIONS] <COMMAND> -r path/to/releases1.yaml -r path/to/releases2.yaml" to provide multiple additional release files. Helm repository options: --helm-repo-stable <URL> Provide a custom Helm stable repository URL [default: https://repo.stackable.tech/repository/helm-stable/] --helm-repo-test <URL> Provide a custom Helm test repository URL [default: https://repo.stackable.tech/repository/helm-test/] --helm-repo-dev <URL> Provide a custom Helm dev repository URL [default: https://repo.stackable.tech/repository/helm-dev/]

$ stackablectl demo list ┌────┬───────────────────────┬─────────┬─────────────────────────────────────────────────────────┐ │ # ┆ NAME ┆ STACK ┆ DESCRIPTION │ ╞════╪═══════════════════════╪═════════╪═════════════════════════════════════════════════════════╡ │ 1 ┆ airflow-scheduled-job ┆ airflow ┆ Activate a simple Airflow DAG to run continuously at a │ │ ┆ ┆ ┆ set interval │ ├╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤ │ 2 ┆ ... ┆ ... ┆ ... │ ├╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤ │ 11 ┆ local-demo-test-env ┆ test ┆ Test demo. Provided with the STACKABLE_DEMO_FILES env │ │ ┆ ┆ ┆ var in the .env file │ └────┴───────────────────────┴─────────┴─────────────────────────────────────────────────────────┘

$ stackablectl demo describe trino-taxi-data DEMO trino-taxi-data DESCRIPTION Demo loading 2.5 years of New York taxi data into S3 bucket, creating a Trino table and a Superset dashboard DOCUMENTATION https://docs.stackable.tech/stackablectl/stable/demos/trino-taxi-data.html STACK trino-superset-s3 LABELS trino, superset, minio, s3, ny-taxi-data