Changed staging CD

[rmgpinto]

ref https://linear.app/ghost/issue/AP-1008

• Staging resource names changed. CD has to reflect those name changes.

[coderabbitai]

Walkthrough

This pull request updates the GitHub Actions workflow in the .github/workflows/build.yml file. The matrix for the deploy-staging job has been expanded to include two new entries that introduce a descriptive region_name for each respective region. Specifically, europe-west4 is now associated with netherlands and europe-west3 with frankfurt. Consequently, the deployment steps have been updated so that the job and service names reference matrix.region_name instead of matrix.region. These changes modify the naming conventions used for the migration job as well as the ActivityPub Queue and API services.

Suggested reviewers

• vershwal

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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: 0

🧹 Nitpick comments (1)

.github/workflows/build.yml (1)

132-137: Matrix Include Update: Descriptive Region Naming

The updated matrix include block now provides a descriptive region_name for each region (e.g., netherlands for europe-west4 and frankfurt for europe-west3). This change improves clarity in subsequent deployment steps while continuing to use matrix.region where the actual deployment region is required.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e1271cc and da3ae0f.

📒 Files selected for processing (1)

• .github/workflows/build.yml (2 hunks)

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

• GitHub Check: Build, Test and Push

🔇 Additional comments (3)

.github/workflows/build.yml (3)

150-151: Migration Job Name Updated

The migration job name now uses matrix.region_name—i.e., stg-${{ matrix.region_name }}-activitypub-migrations—which aligns with the new naming convention. This makes resource identification much clearer.

---

157-159: Service Name Update for ActivityPub Queue

The service name for the ActivityPub Queue has been updated to use matrix.region_name (stg-${{ matrix.region_name }}-activitypub-queue), improving naming clarity. It’s important that the deployment maintains the correct region configuration by still using matrix.region where needed.

---

164-166: Service Name Update for ActivityPub API

Similarly, the ActivityPub API service now references matrix.region_name (stg-${{ matrix.region_name }}-activitypub-api), which enhances readability and consistency in the deployment resource names.