Getting Started Script Checks (Release)
Part of #683
These steps are to be taken once the release branch exists.
In each operator repository, run the following commands. If any updates are
git checkout release-24.11
git pull
# Some of the scripts are in a code/ subdirectory# pushd docs/modules/superset/examples/getting_started# pushd docs/modules/superset/examples/getting_started/codepushd $( find -type d -name getting_started | grep examples) ; cd code 2> /dev/null || true
# Make a fresh cluster (~12 seconds)&& kind create cluster
./getting_started.sh stackablectl
# Make a fresh cluster (~12 seconds)&& kind create cluster
./getting_started.sh helm
popd
Create branches with predictable names so the links below work:
git stash -m " unsaved work" Then use the links below to automatically create applicable PRs for each operator
Replace the items in the task lists below with the applicable Pull Requests (if any).
### Getting Started Script Checks and Updates
- [x] Check getting-started script for airflow-operator @NickLarsenNZ
- [x] ~Check getting-started script for commons-operator~
- [x] Check getting-started script for druid-operator @adwk67
- [x] ~Check getting-started script for edc-operator~
- [x] Check getting-started script for hbase-operator @adwk67
- [x] Check getting-started script for hdfs-operator @adwk67
- [x] ~Check getting-started script for hello-world-operator~
- [x] Check getting-started script for hive-operator @adwk67
- [x] Check getting-started script for kafka-operator @adwk67
- [x] ~Check getting-started script for listener-operator~
- [x] Check getting-started script for nifi-operator @adwk67
- [x] Check getting-started script for opa-operator @NickLarsenNZ
- [x] ~Check getting-started script for secret-operator~
- [x] Check getting-started script for spark-k8s-operator @NickLarsenNZ
- [x] Check getting-started script for superset-operator @NickLarsenNZ
- [x] Check getting-started script for trino-operator @NickLarsenNZ
- [x] Check getting-started script for zookeeper-operator @NickLarsenNZ
Getting Started Script Checks (Release)
Part of #683
Caution
These steps are to be taken once the release branch exists.
In each operator repository, run the following commands. If any updates are
required, open a PR using the applicable link below.
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-24.11.1 origin/release-24.11Then use the links below to automatically create applicable PRs for each operator
using the PR template.
Replace the items in the task lists below with the applicable Pull Requests (if any).