feat(risedev): support launching system rw in risedev-dev

[BugenZhao]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Support launching a cluster using risedev-dev with the risingwave binary installed in the PATH. To enable this, set USE_SYSTEM_RISINGWAVE or configure with ./risedev configure.

This can be useful if one wants to test the behavior of a released version of RisingWave, with the help of risedev-dev to launch some external services.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[BugenZhao]

• feat(risedev): support launching system rw in risedev-dev #18889 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BugenZhao and the rest of your teammates on Graphite

[stdrc]

Then what about RW_VERSION=1.9.0 ./risedev p to run a specific version?

[BugenZhao]

Then what about RW_VERSION=1.9.0 ./risedev p to run a specific version?

Where can we get the binary for a specific version? 🥵 The current idea is to let users decide where to find the binary.

[xxchan]

very good!

[yezizp2012]

LGTM!

[stdrc]

Then what about RW_VERSION=1.9.0 ./risedev p to run a specific version?

Where can we get the binary for a specific version? 🥵 The current idea is to let users decide where to find the binary.

Do we ship binary via homebrew or build from source?

[BugenZhao]

Do we ship binary via homebrew or build from source?

We ship binary on Macs with Apple Silicon.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	e6c7392	ci/scripts/e2e-source-test.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}