init event lib

[jsbroks]

Summary by CodeRabbit

• New Features

  • Streamlined event worker management with unified handling for concurrent processes.
  • Introduced enhanced event processing for deployment-related tasks.
  • Integrated a new events package to broaden the application's functionality.

• Documentation

  • Added introductory documentation for event features.

• Chores

  • Updated deployment configurations to align with new dependency requirements.
  • Introduced improved configuration and lint setups for enhanced code quality.

[coderabbitai]

Warning

Rate limit exceeded

@jsbroks has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 8 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cb3828a and 96dff0c.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (15)

• apps/event-worker/Dockerfile (1 hunks)
• apps/event-worker/package.json (1 hunks)
• apps/event-worker/src/index.ts (1 hunks)
• apps/event-worker/src/workers/index.ts (1 hunks)
• apps/event-worker/src/workers/new-deployment.ts (1 hunks)
• packages/events/.gitignore (1 hunks)
• packages/events/README.md (1 hunks)
• packages/events/eslint.config.js (1 hunks)
• packages/events/package.json (1 hunks)
• packages/events/src/config.ts (1 hunks)
• packages/events/src/index.ts (1 hunks)
• packages/events/src/redis.ts (1 hunks)
• packages/events/src/types.ts (1 hunks)
• packages/events/tsconfig.json (1 hunks)
• packages/validators/src/events/index.ts (1 hunks)

Walkthrough

This pull request updates the event worker configuration to use the events package instead of the secrets package by modifying the Dockerfile and adding a dependency. It refactors the worker initialization in the event worker source to use a consolidated array of workers and introduces new worker files to handle new deployment events. Additionally, a new events package is added with its own configuration, build, linting, TypeScript, and Redis setup files. Finally, an extra event channel for repository releases is added to the validators package.

Changes

File(s)	Change Summary
apps/event-worker/Dockerfile apps/event-worker/package.json	Dockerfile now copies the packages/events/package.json instead of packages/secrets/package.json; dependency on @ctrlplane/events added in package.json.
apps/event-worker/src/index.ts apps/event-worker/src/workers/index.ts apps/event-worker/src/workers/new-deployment.ts	Refactored worker management by introducing an allWorkers array and consolidated worker initialization and shutdown; new worker file for handling new deployment events is added with associated job processing logic.
packages/events/.* packages/events/** (all new files)	New events package created with multiple files including .gitignore, README.md, eslint.config.js, package.json, src/config.ts, src/index.ts, src/redis.ts, src/types.ts, and tsconfig.json to set up event handling, worker creation, Redis configuration, and TypeScript settings.
packages/validators/src/events/index.ts	Added new enum member ReleaseNewRepository to the Channel enum.

Sequence Diagram(s)

sequenceDiagram
    participant D as Deployment Event
    participant NDW as NewDeploymentWorker
    participant GDR as getDeploymentResources
    participant DB as Database
    participant Q as Evaluated Queue

    D->>NDW: Trigger new deployment job
    NDW->>GDR: Invoke getDeploymentResources(tx, deployment)
    GDR->>DB: Query system and environments
    DB-->>GDR: Return system details and environments
    GDR-->>NDW: Return list of resources
    NDW->>Q: Enqueue job data for processing

Loading

Poem

I’m a bunny in the code field, hopping with delight,
New workers and events make my day so bright.
Channels open wide, with flows crisp and neat,
From deployments to queues, the changes are sweet.
With every keystroke and hop, our system sings,
A celebration of code and all the joy it brings! 🐰✨

---

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.

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.