feat : re organize modules

[rajadilipkolli]

Summary by CodeRabbit

• Chores
  • Updated workflow paths in GitHub Actions to ensure correct directory targeting and streamlined CI/CD processes across multiple Kafka and Spring Boot related workflows.
  • Reordered and added new entries in the list of sample projects in the README.md file.
  • Removed sections related to Spring Cloud and Spring Integration DSL in README.md files for better focus on Spring Boot implementations.

[coderabbitai]

Warning

Rate Limit Exceeded

@rajadilipkolli has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 58 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

Files that changed from the base of the PR and between 38e138d and aa1dcba.

Walkthrough

The recent updates to the GitHub workflows focus on refining the directory paths and configurations across various Kafka integration and deployment scenarios. This ensures that the automated actions are triggered correctly and efficiently, aligning with the restructured project directories.

Changes

Files Affected	Summary of Changes
.github/workflows/kafka-sample-spring-cloud.yml .github/workflows/kafka-sample-spring-modulith.yml .github/workflows/kafka-spring-boot-integration-dsl.yml .github/workflows/kafka-spring-boot-multiple-producers-consumers.yml .github/workflows/kafka-spring-boot.yml	Updated paths for action triggers to reflect new directory structures; adjustments in working directories; version updates for actions/checkout.
README.md	Reordered and added new entries in the list of sample projects integrating with Kafka, including DSL integration, Spring Boot examples, Kafka Streams implementation, Kafka implementation using cloud bindings, and Outbox Pattern Implementation using Modulith.
kafka-sample/README.md	Removed the section related to producing and consuming messages using Spring Cloud.
kafka-spring-boot/README.md	Removed the section on producing and consuming messages using Spring Integration DSL.
.github/labeler.yml	Added new components like dsl-integration, cloud, and modulith with corresponding file paths in the labeler configuration file.

Possibly related issues

• Dependency Dashboard #72: The issue discusses defining workflows for different Kafka components, which aligns with the changes made in the PR to update paths and configurations in workflow files.
  • Reasoning: The PR's updates to GitHub Actions workflows directly relate to the issue's objective of defining and updating workflows for Kafka components.

Poem

🐰🌟
In the land of code and commit,
A rabbit hopped, making things fit.
Paths were tweaked, directories aligned,
Ensuring that no file was left behind.
Now each script runs just right,
In the GitHub land, what a sight!
🌟🐰

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.