Skip to content

Reintroduce infrastructure launch Mise command#603

Merged
forstmeier merged 1 commit intomasterfrom
06-19-reintroduce_infrastructure_launch_mise_command
Jun 19, 2025
Merged

Reintroduce infrastructure launch Mise command#603
forstmeier merged 1 commit intomasterfrom
06-19-reintroduce_infrastructure_launch_mise_command

Conversation

@forstmeier
Copy link
Copy Markdown
Collaborator

@forstmeier forstmeier commented Jun 19, 2025

Overview

Changes

  • add back Mise command

Comments

Trying this out to fix the uv dependency error but I'm like 90% sure this won't actually work.

Summary by CodeRabbit

  • Chores
    • Simplified the deployment process by consolidating multiple steps into a single command.
    • Introduced a new task for launching cloud infrastructure, making deployment easier to manage.
    • Removed the explicit Python version lock from the infrastructure configuration.

Copilot AI review requested due to automatic review settings June 19, 2025 19:39
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 19, 2025

Walkthrough

The deployment process was refactored by introducing a new "infrastructure:up" task in .mise.toml, consolidating multiple deployment commands into a single task. The GitHub Actions workflow now calls this unified task, and the .python-version file in the infrastructure directory was removed.

Changes

File(s) Change Summary
.github/workflows/deploy.yaml Replaced multi-step deployment script with a single mise tasks run infrastructure:up command.
.mise.toml Added new infrastructure:up task to automate deployment steps in one command.
infrastructure/.python-version Deleted Python version lock file (.python-version).

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Mise
    participant Infrastructure Directory

    GitHub Actions->>Mise: Run "infrastructure:up" task
    Mise->>Infrastructure Directory: cd infrastructure
    Mise->>Infrastructure Directory: uv run pulumi up --yes
    Mise->>Infrastructure Directory: nu ping.nu
Loading

Possibly related PRs

Suggested labels

infrastructure, codex

Suggested reviewers

  • chrisaddy

Poem

A rabbit hopped through code so neat,
Wrapping commands in one tidy sheet.
No more Python lock to find,
Just one task, streamlined and kind.
Now with a single call,
The cloud stands tall—
Deployment’s never been so sweet! 🐇✨


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
Copy Markdown
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@forstmeier forstmeier added this to the Refactor milestone Jun 19, 2025
@graphite-app
Copy link
Copy Markdown

graphite-app Bot commented Jun 19, 2025

Graphite Automations

"Assign author to pull request" took an action on this PR • (06/19/25)

1 assignee was added to this PR based on John Forstmeier's automation.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR reintroduces a standardized Mise task for launching cloud infrastructure and updates the CI workflow to use it.

  • Removed the pinned Python version file
  • Added an infrastructure:up task in .mise.toml
  • Updated the GitHub Actions deploy workflow to invoke the new Mise task

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
infrastructure/.python-version Removed pinned Python version setting
.mise.toml Added infrastructure:up task for launching infrastructure
.github/workflows/deploy.yaml Replaced inline pulumi commands with mise tasks run
Comments suppressed due to low confidence (3)

.mise.toml:88

  • [nitpick] Using a colon in the task name can be confusing for users; consider renaming to a more conventional pattern like infrastructure-up or infra:up.
[tasks."infrastructure:up"]

.github/workflows/deploy.yaml:39

  • The workflow step assumes the mise CLI is already installed in the runner; add a setup step to install or verify mise before invoking the task.
          command: mise tasks run infrastructure:up

@graphite-app graphite-app Bot requested a review from chrisaddy June 19, 2025 19:42
Copy link
Copy Markdown
Contributor

@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: 0

🧹 Nitpick comments (1)
.mise.toml (1)

88-95: Suggest Enhanced Logging and Environment Validation

Consider enabling command tracing (set -x) for better visibility and adding a prerequisite check for critical environment variables (e.g., PULUMI_STACK) before deployment:

 [tasks."infrastructure:up"]
 run = """
-set -e
+set -ex
+if [ -z "$PULUMI_STACK" ]; then
+  echo "ERROR: PULUMI_STACK not set"
+  exit 1
+fi
 cd infrastructure
 uv run pulumi up --yes
 nu ping.nu
 """
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a49ff03 and b01926b.

📒 Files selected for processing (3)
  • .github/workflows/deploy.yaml (1 hunks)
  • .mise.toml (1 hunks)
  • infrastructure/.python-version (0 hunks)
💤 Files with no reviewable changes (1)
  • infrastructure/.python-version
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Python tests
🔇 Additional comments (3)
.mise.toml (1)

88-95: Infrastructure Task Implementation Looks Good

The new infrastructure:up task correctly centralizes the Pulumi deployment steps under a single command.

.github/workflows/deploy.yaml (2)

39-39: GitHub Action Invocation Updated

The workflow now cleanly delegates the deployment to the new infrastructure:up task via mise tasks run.


39-39: Verify mise CLI Availability

Ensure the runner has the mise CLI available (e.g., via Flox or another installer) before this step, or add an explicit installation/verification step to avoid failures.

@forstmeier forstmeier merged commit ffca1af into master Jun 19, 2025
6 checks passed
@forstmeier forstmeier deleted the 06-19-reintroduce_infrastructure_launch_mise_command branch June 19, 2025 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants