chore: use separate ports for dev-lima

[jason-lynch]

Summary

Using the same ports made it too easy to mix up environments and make broken clusters. This change increments all port numbers in the dev-lima environment by 10 to keep everything on separate ports from the compose environment.

Notes for Reviewers

You'll want to open a new terminal to get the dev-env.zsh changes and run make dev-lima-reset to stop and remove your current dev-lima cluster.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e5801b32-27b7-41ae-8463-8057668805f4

📥 Commits

Reviewing files that changed from the base of the PR and between a7e1e07 and ad5260f.

📒 Files selected for processing (3)

• hack/dev-env.zsh
• lima/run.sh
• lima/vars.yaml

---

📝 Walkthrough

Walkthrough

Port configuration shifts from ranges 3000–3005 to 3010–3015 for HTTP endpoints and 2389–2589 for etcd services across development environment setup scripts and Lima VM configuration files.

Changes

Cohort / File(s)	Summary
Port Number Updates hack/dev-env.zsh, lima/run.sh, lima/vars.yaml	REST/HTTP endpoint ports remapped from 3000–3005 to 3010–3015; etcd peer and client ports adjusted to 2390–2590 range. Affects host registration, dynamic port selection via CP_ENV variable, and machine configuration in Lima VMs.

Poem

🐰 Bounce, bounce, those ports now play,
In the 3010s they stay, hip hooray!
Lima VMs and etcd align,
With numbers so fresh, configuration divine! 🚀

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	The description includes Summary and Notes for Reviewers sections, but is missing Changes, Testing, Checklist, and other template sections.	Complete the description by adding the Changes section (bulleted list of modifications), Testing section with verification steps, and Checklist items to confirm testing, documentation, and issue linking were addressed.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: incrementing ports for dev-lima to separate them from compose environment.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/separate-dev-lima-ports

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}