Skip to content

Conversation

kristapsk
Copy link
Member

@kristapsk kristapsk commented Jun 11, 2025

Helps me to do some finalize-nakamochi.sh tests sometimes from local LiveCD Linux virtual machines without mkpasswd present and possibility to install (like Gentoo minimal installation CD). And adding ssh authorized key from this script is very useful in general, avoids extra manual steps later.

Summary by CodeRabbit

  • New Features

    • Added support for specifying an SSH authorized public key file for root user access.
    • Introduced an option to skip setting the root password, enhancing setup flexibility.
  • Bug Fixes

    • Improved validation to ensure the SSH authorized key file exists before use.

Copy link

coderabbitai bot commented Jun 11, 2025

"""

Walkthrough

The script finalize-nakamochi.sh was enhanced to include an optional SSH authorized key file argument and a --skip-passwd flag to bypass setting the root password. Usage instructions, argument parsing, and conditional logic were updated to validate inputs and apply these options during image finalization.

Changes

File(s) Change Summary
tools/finalize-nakamochi.sh Added optional SSH authorized key argument, --skip-passwd flag, updated usage, argument parsing, validation, and conditional logic for password setting and SSH key appending.

Poem

A script now smarter, with keys and a flag,
Root’s password can rest, no need for a tag.
SSH keys can hop in, with a skip and a cheer,
Flexibility’s here, for all engineers!
🐇✨
"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f7ea4a and 5750a47.

📒 Files selected for processing (1)
  • tools/finalize-nakamochi.sh (8 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tools/finalize-nakamochi.sh
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
tools/finalize-nakamochi.sh (3)

39-47: Refine usage message for optional SSH key.
The current syntax [/mnt/usd [/mnt/ssd [ssh_authorized_key]]] is correct but could be clearer. Consider using explicit placeholders and angle‐brackets for readability:

Usage: $(basename "$0") [options] <USD_DEVICE> <SSD_DEVICE> [<USD_MOUNT>] [<SSD_MOUNT>] [<SSH_AUTHORIZED_KEY>]

98-103: Make package manager-agnostic suggestion.
The error message directs users to apt install whois, which may not apply across distributions. Consider a generic notice:

Error: mkpasswd not found (install via the 'whois' package on your distro).

328-335: Streamline authorized key installation.
Appending the key works, but you can use install for atomic directory creation and permissions:

+ install -d -m 700 "$USD_MOUNT_POINT/root/.ssh"
+ install -m 600 "$SSH_AUTHORIZED_KEY" "$USD_MOUNT_POINT/root/.ssh/authorized_keys"
- mkdir -p "$USD_MOUNT_POINT"/root/.ssh
- cat "$SSH_AUTHORIZED_KEY" >> "$USD_MOUNT_POINT"/root/.ssh/authorized_keys
- chmod 600 "$USD_MOUNT_POINT"/root/.ssh/authorized_keys
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 40ffa70 and 1a239ac.

📒 Files selected for processing (1)
  • tools/finalize-nakamochi.sh (8 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (5)
tools/finalize-nakamochi.sh (5)

63-63: Initialize skip_passwd flag.
Defaulting skip_passwd=0 is appropriate to maintain current behavior.


72-75: Handle --skip-passwd option.
The new case branch correctly parses and shifts the --skip-passwd flag.


114-114: Capture SSH authorized key argument.
Assigning the fifth positional argument ($5) to SSH_AUTHORIZED_KEY after option parsing is correct.


290-297: Guard password setup in test-image block.
The skip_passwd checks correctly skip setting a root password and the accompanying echo when flagged.


303-306: Guard password setup in production block.
The conditional around mkpasswd ensures no password is set when skipping. This aligns with the new flag.

@kristapsk kristapsk merged commit 2cc8889 into nakamochi:master Jun 11, 2025
2 checks passed
@kristapsk kristapsk deleted the skip-mkpasswd branch June 11, 2025 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant