add boot_b mapping for ride4 boards

[bennyz]

Summary by CodeRabbit

• Chores
  • Enhanced boot partition handling for specific device targets to ensure proper multi-partition flashing.
  • Extended partition configuration support for additional device platforms.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR extends boot partition support for specific ride4* and ridesx4* targets. The push_artifact.sh script now duplicates boot_a files to boot_b for these targets during multi-layer artifact preparation, while partition rules configuration is updated to include boot_b in the partition include lists for affected targets.

Changes

Cohort / File(s)	Summary
Boot Partition Duplication Logic internal/common/tasks/scripts/push_artifact.sh	Adds target-specific boot partition duplication: for ride4* and ridesx4* targets, copies boot_a.* files to boot_b.* within the parts_dir processing if boot_b.* does not already exist, ensuring both boot partitions are available for flashing.
Partition Configuration Updates internal/controller/operatorconfig/controller.go	Extends partition-rules.yaml configuration to add boot_b to the include lists for ridesx4, ridesx4_scmi, and ride4_sa8775p_sx_r3 targets alongside existing system_a, system_b, and boot_a partitions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• use multi layer push #55 — Introduces the multi-layer push flow in push_artifact.sh that this PR's boot partition duplication directly extends.
• add included list of partitions #72 — Adds partition-config/default-partitions framework that this PR's partition rules updates build upon.

Poem

🐰 Two boots are better than one, you see,

Boot_a dupes to boot_b so merrily,

For ride4 and ridesx4 with care,

Both partitions flashing, a perfect pair! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly aligns with the main changes: adding boot_b mapping/configuration for ride4 and related board targets across both files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

internal/common/tasks/scripts/push_artifact.sh (1)

218-218: Nit: sed 's/boot_a/boot_b/' replaces the first occurrence in the full path, not just the filename.

If parts_dir ever contained the substring boot_a, the substitution would corrupt the path. Currently safe given the naming convention (${exportFile}-parts), but anchoring to the basename would be more defensive:

Suggested hardening

-        boot_b_file=$(echo "$boot_a_file" | sed 's/boot_a/boot_b/')
+        boot_b_file="${parts_dir}/$(basename "$boot_a_file" | sed 's/boot_a/boot_b/')"

---

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.}