Added —dry-run command

[pec1985]

Summary by CodeRabbit

• New Features
  • Introduced a --dry-run option for the deployment command, allowing users to save the deployment package locally without uploading or deploying.
  • Provides clear output indicating the location and details of the saved package when using the dry-run option.

[coderabbitai]

Walkthrough

A new --dry-run flag was added to the cloudDeployCmd command in cmd/cloud.go. When specified, the deployment process saves the packaged zip file to a given directory and exits, skipping the upload and deployment steps. The flag is documented and integrated into the command's workflow.

Changes

File(s)	Change Summary
cmd/cloud.go	Added --dry-run string flag to cloudDeployCmd; implemented logic to copy the zip file to a specified directory and exit early; updated help text and flag definitions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant cloudDeployCmd
    participant FileSystem

    User->>cloudDeployCmd: Run with --dry-run flag
    cloudDeployCmd->>cloudDeployCmd: Package project into zip
    cloudDeployCmd->>FileSystem: Copy zip file to specified directory
    alt Copy successful
        cloudDeployCmd->>User: Output success message/JSON and exit
    else Copy fails
        cloudDeployCmd->>User: Output error and exit
    end

Loading

Estimated code review effort

1 (~5 minutes)

Poem

A flag called "dry-run" hops in with glee,
Saving zips to a folder, deployment set free.
No uploads today, just a copy and done—
The cloud takes a break, but the rabbit still runs!
🐇✨

---

📜 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 5be73a9 and 35a9fda.

📒 Files selected for processing (1)

• cmd/cloud.go (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• cmd/cloud.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Test CLI Upgrade Path (windows-latest)
• GitHub Check: Analyze (go)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch DRYRUN

---

🪧 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 generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7993756 and 5be73a9.

📒 Files selected for processing (1)

• cmd/cloud.go (4 hunks)

🔇 Additional comments (3)

cmd/cloud.go (3)

170-177: LGTM - Clear documentation and examples

The help text properly documents the new --dry-run flag and includes a helpful example. The documentation clearly explains the flag's purpose.

---

200-200: LGTM - Consistent flag retrieval pattern

The flag retrieval follows the established pattern used for other flags in this function.

---

1001-1001: LGTM - Proper flag definition

The flag definition is correct with an appropriate description that matches the implemented functionality.

[robindiddams]

use bool?