Skip to content

tracking: Check and update getting-started scripts before SDP Release 26.3.0 #826

@sbernauer

Description

@sbernauer

Getting Started Script Checks (Pre-Release)

Part of #812

In each operator repository, run the following commands. If any updates are
required, open a PR using the applicable link below.

# Some of the scripts are in a code/ subdirectory
# pushd docs/modules/superset/examples/getting_started
# pushd docs/modules/superset/examples/getting_started/code
pushd $(fd -td getting_started | grep examples); cd code 2>/dev/null || true

# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh stackablectl

# Make a fresh cluster (~12 seconds)
kind delete cluster && kind create cluster
./getting_started.sh helm

popd

Tip

Create branches with predictable names so the links below work.

git stash -m "unsaved work"
git fetch origin
git checkout -b fix/getting-started-pre-26.3.0 origin/main

Then use the links below to automatically create applicable PRs for each operator
using the PR template.

Getting Started Script Checks and Updates

Replace the items in the task list below with the applicable Pull Requests (if any).

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions