Cloned projects need an .env file

[jhaynie]

• Import and then clone new project and you are missing .env file
• Also allow env list and get to be masked optionally and optionally include project keys in list

Summary by CodeRabbit

• New Features
  • Added options to mask secrets and include project keys when viewing environment variables.
  • Introduced new command-line flags to control secret masking and inclusion of project keys in environment variable commands.
  • Improved handling and automatic creation of .env files during development setup.

[coderabbitai]

Walkthrough

The changes introduce two new boolean parameters, shouldMask and includeProjectKeys, to the GetProject method and update all its call sites accordingly. Command-line flags are added to allow users to control these parameters in relevant CLI commands, affecting how project data and secrets are retrieved and displayed. Additionally, environment file handling in the dev command is enhanced to create a .env file if missing.

Changes

File(s)	Change Summary
internal/project/project.go	Updated GetProject method signature to include shouldMask and includeProjectKeys booleans; updated API URL.
cmd/cloud.go, cmd/dev.go, cmd/env.go	Updated calls to GetProject to pass new boolean parameters; added CLI flags (mask, include-project-keys) where needed; adjusted error messages and environment file handling logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI_Command
    participant Project
    participant API

    User->>CLI_Command: Run env/list/get/delete or dev/cloud command
    CLI_Command->>Project: GetProject(ctx, logger, url, token, shouldMask, includeProjectKeys)
    Project->>API: GET /project?mask=shouldMask&includeProjectKeys=includeProjectKeys
    API-->>Project: Project data (with/without secrets masked, with/without project keys)
    Project-->>CLI_Command: ProjectData
    CLI_Command-->>User: Output (according to flags)

Loading

Suggested reviewers

• pec1985

Poem

A hop, a skip, with flags anew,
Now secrets mask or show on cue.
With keys included—yes or no—
The project fetch is in control!
So rabbits cheer, with ears held high,
For CLI commands that now comply.
🐇✨

---

📜 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 4f5a5de and 15e12aa.

📒 Files selected for processing (1)

• cmd/dev.go (2 hunks)

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

• cmd/dev.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

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

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

[potofpie]

✅