feat: add kurtosis package

[MSevey]

Overview

Extract kurtosis package from GM tutorial.

Closes rollkit/rollkit#1766

Summary by CodeRabbit

• New Features

  • Introduced a configuration for the Rollkit Local DA Kurtosis package.
  • Added functionality to set up a local DA service and configure its ports, returning an address for rollups.

• Chores

  • Updated CI workflow to trigger on tags starting with 'v'.
  • Simplified version patterns for the Docker build and publish workflow triggers.
  • Added Dockerfile lint job with a specific failure threshold to the lint workflow.

[coderabbitai]

Walkthrough

The recent changes across several configuration files focus on refining CI/CD processes and supporting new features for local Data Aggregator services. Changes include broadening version tag triggers for workflows, adding a Dockerfile lint job, and configuring Kurtosis for Rollkit Local DA. Additionally, a new function is introduced in main.star to set up a local DA service, enhancing rollup configuration capabilities.

Changes

File	Summary
.github/workflows/ci_release.yml	Modified tag trigger condition to include all versions starting with 'v'.
.github/workflows/docker-build-publish.yml	Simplified the version patterns for triggering the workflow, focusing on a wildcard approach for tags.
.github/workflows/lint.yml	Added a new job dockerfile-lint utilizing a reusable Dockerfile lint workflow with a failure threshold.
kurtosis.yml	Introduced configuration settings for the Rollkit Local DA Kurtosis package.
main.star	Added run(plan) function to set up a local DA service, configure ports, and return addresses for rollups.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Docker
    participant Kurtosis
    participant DA_Service

    User->>GitHub Actions: Push code with 'v' tag
    GitHub Actions->>GitHub Actions: Trigger CI workflows
    GitHub Actions->>Docker: Run Dockerfile linting
    GitHub Actions->>Kurtosis: Apply configuration settings
    User->>DA_Service: Initiate `run(plan)` function
    DA_Service->>DA_Service: Setup local DA, configure ports
    DA_Service-->>User: Return rollup addresses

Loading

Poem

> In the realm of code so slick,
> Tags of 'v' now do the trick 🐇,
> Linting Docker never fails,
> Setting sails with Kurtosis tales.
> Data Aggregates run with speed,
> All for the devs' every need 🌟.

---

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.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 19d7b14 and 6862176.

Files selected for processing (5)

• .github/workflows/ci_release.yml (1 hunks)
• .github/workflows/docker-build-publish.yml (1 hunks)
• .github/workflows/lint.yml (1 hunks)
• kurtosis.yml (1 hunks)
• main.star (1 hunks)

Files skipped from review due to trivial changes (4)

• .github/workflows/ci_release.yml
• .github/workflows/docker-build-publish.yml
• .github/workflows/lint.yml
• kurtosis.yml

Additional comments not posted (4)

main.star (4)

3-12: Good use of PortSpec for defining ports.

The port specification and mapping look correct. This ensures that the service will listen on the defined port using the specified protocols.

---

13-20: Service configuration is well-structured.

The service configuration uses the correct image and maps the defined ports. Public ports are also correctly specified.

---

22-25: Ensure the service is reachable.

The address formation for the local DA service is correct. Ensure that the service is reachable at the formed address.

---

27-27: LGTM!

The function correctly returns the address of the local DA service.

[tuxcanfly]

OK.