chore: move handle-provider-scan util to events package

[adityachoudhari26]

Summary by CodeRabbit

• Chores

  • Updated internal dependencies and reorganized import sources to streamline package usage.
  • Added a dependency on the rule engine in the events package and removed an events dependency from the rule engine package.

• Refactor

  • Consolidated and updated import paths for improved code organization.
  • Removed and restructured certain exports to centralize resource provider scan functionality in the events package.

[coderabbitai]

Walkthrough

This change reorganizes the import and export structure for resource scan and provider scan logic, moving related types and functions from the @ctrlplane/job-dispatch package to the @ctrlplane/events package. Dependency references and package exports are updated accordingly, and redundant or obsolete files are removed.

Changes

File(s)	Change Summary
apps/event-worker/src/workers/resource-scan/index.ts apps/event-worker/src/workers/resource-scan/utils/extract-variables.ts apps/webservice/src/app/api/v1/resource-providers/[providerId]/set/route.ts apps/pty-proxy/src/controller/agent-socket.ts	Updated imports for ResourceToInsert and handleResourceProviderScan to use @ctrlplane/events instead of @ctrlplane/job-dispatch. Consolidated related imports.
packages/events/package.json	Added @ctrlplane/rule-engine as a workspace dependency.
packages/events/src/index.ts	Added export for all members from ./resource-provider-scan/handle-provider-scan.js.
packages/events/src/resource-provider-scan/handle-provider-scan.ts	Changed imports for Channel and getQueue to use local relative paths.
packages/job-dispatch/src/index.ts	Removed export of ./resource/index.js.
packages/job-dispatch/src/resource/index.ts	Deleted file; previously re-exported resource scan and grouping logic.
packages/rule-engine/package.json	Removed dependency on @ctrlplane/events.

Sequence Diagram(s)

sequenceDiagram
    participant Webservice
    participant EventsPkg as @ctrlplane/events
    participant EventWorker

    Webservice->>EventsPkg: import handleResourceProviderScan
    EventWorker->>EventsPkg: import ResourceToInsert, handleResourceProviderScan, Channel, getQueue
    EventsPkg->>EventsPkg: Export handleResourceProviderScan and related types/functions

Loading

Possibly related PRs

• ctrlplanedev/ctrlplane#498: Refactors resource deletion logic and introduces asynchronous queue handling, related to resource provider scan and event channel handling.
• ctrlplanedev/ctrlplane#440: Initializes the @ctrlplane/events package and adds it as a dependency to the event worker, setting the stage for the reorganization in this PR.
• ctrlplanedev/ctrlplane#510: Adds variable extraction functionality and updates the resource scan worker, overlapping with import and export changes in this PR.

Poem

In the warren of code, things shift and align,
Resource scans now gather where events intertwine.
Imports hop over, exports leap too,
Old paths are burrowed, new ones debut.
With a twitch of the nose, dependencies pruned—
This rabbit’s delighted: the modules are tuned! 🐇

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0af5bce and f27955f.

📒 Files selected for processing (1)

• apps/pty-proxy/src/controller/agent-socket.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• apps/pty-proxy/src/controller/agent-socket.ts

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

• GitHub Check: Typecheck
• GitHub Check: Lint
• GitHub Check: build (linux/amd64)
• GitHub Check: build (linux/amd64)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • 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.

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.