Skip to content

Fix breaking deployment command#602

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

Fix breaking deployment command#602
forstmeier merged 1 commit intomasterfrom
06-19-fix_breaking_deployment_command

Conversation

@forstmeier
Copy link
Copy Markdown
Collaborator

@forstmeier forstmeier commented Jun 19, 2025

Overview

Changes

  • update "deploy" command

Comments

Quick fix.

Summary by CodeRabbit

  • Chores
    • Updated deployment workflow to use a multi-step script for infrastructure setup and verification.

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

coderabbitai Bot commented Jun 19, 2025

Walkthrough

The deployment workflow was updated to replace a single command with a multi-step shell script. The new script changes to the infrastructure directory, applies Pulumi infrastructure changes using a different invocation, and runs an additional command after deployment.

Changes

File(s) Change Summary
.github/workflows/deploy.yaml Deployment step changed from a single command to a multi-line script: directory change, Pulumi command update, and added post-deployment command.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Infrastructure Directory
    participant Pulumi
    participant nu

    GitHub Actions->>Infrastructure Directory: cd infrastructure
    GitHub Actions->>Pulumi: uv run pulumi up --yes
    GitHub Actions->>nu: nu ping.nu
Loading

Possibly related PRs

  • Add deployment workflow #532: Modifies the deployment workflow, similar to the changes in this PR, by altering command invocation and sequence.

Suggested labels

codex

Suggested reviewers

  • chrisaddy

Poem

In the warren, scripts now hop in a row,
First to the burrow where infrastructures grow.
Pulumi leaps up, with a "yes" in its paw,
Then nu pings a tune—oh, what a hurrah!
Rabbits love order, and so does this flow.
🐇✨🚀


📜 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 a5da7bf and 44625bf.

📒 Files selected for processing (1)
  • .github/workflows/deploy.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/deploy.yaml
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Python tests

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
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 fixes a broken deployment command in the GitHub Actions workflow. The changes replace a single-line command with a multi-line block to change directories, run the pulumi command, and execute an additional command.

  • Replaces "mise run infrastructure:up" with a multi-command block.
  • Introduces steps to change the working directory and execute two distinct commands.

Comment thread .github/workflows/deploy.yaml
@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

@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)
.github/workflows/deploy.yaml (1)

39-43: Use working-directory instead of cd
Relying on an inline cd infrastructure can be brittle. Make the working directory explicit by using the step-level working-directory property so that all commands run in the correct context.

Example diff:

@@ -33,8 +33,9 @@
       - name: Deploy with Pulumi
         uses: flox/activate-action@v1
-        env:
+        working-directory: infrastructure
+        env:
           PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
         with:
           command: |
-            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 3d9142c and a5da7bf.

📒 Files selected for processing (1)
  • .github/workflows/deploy.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Python tests
🔇 Additional comments (2)
.github/workflows/deploy.yaml (2)

40-41: Verify Pulumi invocation syntax
Confirm that uv run pulumi up --yes matches your Flox wrapper’s expected syntax and that it invokes the correct Pulumi stack (e.g., ensure PULUMI_STACK or equivalent is set upstream).


42-42: Validate nu ping.nu target
Double-check that nu ping.nu corresponds to a real Flox task or script in your infrastructure directory so it won’t fail silently.

@forstmeier forstmeier force-pushed the 06-19-fix_breaking_deployment_command branch from a5da7bf to 44625bf Compare June 19, 2025 17:51
@forstmeier forstmeier merged commit a49ff03 into master Jun 19, 2025
6 checks passed
@forstmeier forstmeier deleted the 06-19-fix_breaking_deployment_command branch June 19, 2025 17:56
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