Skip to content

Changed ci/cd to support second pub/sub topic#867

Merged
rmgpinto merged 1 commit intomainfrom
cicd-pubsub-second-topic
Jun 17, 2025
Merged

Changed ci/cd to support second pub/sub topic#867
rmgpinto merged 1 commit intomainfrom
cicd-pubsub-second-topic

Conversation

@rmgpinto
Copy link
Copy Markdown
Collaborator

ref https://linear.app/ghost/issue/PROD-1953

  • Changed ci/cd to support the second pub/sub topic. Includes deployments to two new services: ghost-queue and fedify-queue.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 17, 2025

Walkthrough

The CI/CD workflow configuration was modified to split the single environment variable TF_VAR_queue_image into two separate variables: TF_VAR_fedify_queue_image and TF_VAR_ghost_queue_image for Terraform deployments triggered by pull requests. Additional deployment steps were added in both staging and production jobs to deploy two new Cloud Run services, activitypub-fedify-queue and activitypub-ghost-queue, in each region. These new services are deployed alongside the existing activitypub-queue service and use the same Docker image version and commit SHA labeling.

Possibly related PRs


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.

ref https://linear.app/ghost/issue/PROD-1953

- Changed ci/cd to support the second pub/sub topic. Includes
deployments to two new services: ghost-queue and fedify-queue.
@rmgpinto rmgpinto force-pushed the cicd-pubsub-second-topic branch from 8c83c21 to e68a3f9 Compare June 17, 2025 09:19
@rmgpinto rmgpinto enabled auto-merge (squash) June 17, 2025 09:19
Copy link
Copy Markdown

@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

♻️ Duplicate comments (2)
.github/workflows/cicd.yml (2)

451-460: Duplicate of staging Fedify queue logic
The stg-*-activitypub-ghost-queue deploy block is structurally identical to the Fedify step above. Consider the same refactor suggestion to DRY these two blocks via a loop or anchors.


542-550: Duplicate of production Fedify queue logic
This prd-*-activitypub-ghost-queue step repeats the same structure. Apply the same DRY refactor for consistency.

🧹 Nitpick comments (2)
.github/workflows/cicd.yml (2)

441-450: Consider DRYing the staging queue deployments
The new step for stg-${{ matrix.region_name }}-activitypub-fedify-queue looks correct, but it nearly duplicates the existing queue deploy block. You could consolidate all queue service names into a matrix or use YAML anchors to reduce repetition.


532-540: DRY up production Fedify queue step
The prd-${{ matrix.region_name }}-activitypub-fedify-queue deployment mirrors the existing queue block. Extract the queue names to a matrix or YAML anchor to avoid copy-pasting.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ced6a46 and e68a3f9.

📒 Files selected for processing (1)
  • .github/workflows/cicd.yml (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build, Test and Push
🔇 Additional comments (1)
.github/workflows/cicd.yml (1)

309-310: Ensure Terraform modules consume the new variables
You’ve split TF_VAR_queue_image into TF_VAR_fedify_queue_image and TF_VAR_ghost_queue_image, which aligns with the new services. Double-check that your Terraform configs (e.g. in the staging and production environment folders of the infra repo) declare and use these variables so they actually drive the new deployments.

@rmgpinto rmgpinto merged commit 06e5b53 into main Jun 17, 2025
10 checks passed
@rmgpinto rmgpinto deleted the cicd-pubsub-second-topic branch June 17, 2025 09:29
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.

1 participant