chore: update helm to latest parseable release v2.0.0

[nitisht]

Summary by CodeRabbit

• New Features

  • Upgraded the release to version 2.0.0 with a refined chart description highlighting fast observability on S3.
  • Enhanced metadata now provides clearer dependency and release information for the Parseable chart.

• Chores

  • Updated the deployment configuration to reference the latest image version.
  • Refreshed release timestamps to ensure consistency across documentation and release records.

[coderabbitai]

Walkthrough

This pull request updates the Helm chart configuration for the Parseable application. The changes update metadata in the Helm chart files by modifying the description, version, appVersion, and the image tag from v1.7.5 to v2.0.0. Additionally, the index file is enhanced with new entries and refreshed timestamps, including detailed metadata such as dependencies, digest, icon, and maintainer information.

Changes

Files	Summary
helm/Chart.yaml, helm/values.yaml	Updated metadata: changed description to “Helm chart for Parseable - Fast Observability on S3” and upgraded version, appVersion, and image tag from v1.7.5 to v2.0.0.
index.yaml	Refreshed created timestamps and added a new “parseable” entry with dependencies, detailed metadata (digest, icon, maintainers, URLs), and version information.
src/event/format/known_schema.rs	Modified documentation comment for the check_or_extract method to adjust indentation for clarity.
src/storage/localfs.rs	Optimized the get_bucket_name method by replacing .last() with .next_back() for more efficient retrieval of the last element from an iterator.
src/utils/arrow/mod.rs	Updated the add_parseable_fields function to use std::iter::repeat_n instead of std::iter::repeat(...).take(...) for constructing a StringArray.

Suggested labels

for next release

Suggested reviewers

• de-sh

Poem

I'm a rabbit hopping with glee,
For a new Helm chart release has come to be.
Metadata updated with a careful touch,
Version 2.0.0 means we've improved so much.
I nibble on code with a joyful heart,
Celebrating these changes—a fresh, vibrant start!
🐇🌟

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0553347 and 5b0ca47.

📒 Files selected for processing (3)

• src/event/format/known_schema.rs (1 hunks)
• src/storage/localfs.rs (1 hunks)
• src/utils/arrow/mod.rs (1 hunks)

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

• src/event/format/known_schema.rs
• src/storage/localfs.rs

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

• GitHub Check: Build Default x86_64-apple-darwin
• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments
• GitHub Check: coverage
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments

🔇 Additional comments (1)

src/utils/arrow/mod.rs (1)

141-143: Improved iterator usage with repeat_n

The change from std::iter::repeat(value).take(row_count) to std::iter::repeat_n(value, row_count) is a welcome improvement. The repeat_n function (added in Rust 1.58.0) provides a more direct and potentially more efficient way to create an iterator that repeats a value a fixed number of times, without first creating an infinite iterator and then limiting it.

This modernizes the code while maintaining identical functionality.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

index.yaml (1)

34-58: New parseable 2.0.0 entry review.

A new index entry for the parseable chart version 2.0.0 has been added. The URL correctly points to the new release package, and the updated created timestamp reflects the new release date.

However, note that the description field in this new entry remains as "Helm chart for Parseable Server" while the Chart.yaml now uses "Helm chart for Parseable - Fast Observability on S3." For consistency across the helm files, consider updating this description here to match the updated one.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 40876cd and 0553347.

📒 Files selected for processing (3)

• helm/Chart.yaml (1 hunks)
• helm/values.yaml (1 hunks)
• index.yaml (59 hunks)

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

• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Default x86_64-apple-darwin
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: coverage
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments

🔇 Additional comments (4)

helm/values.yaml (1)

4-4: Update image tag successfully.

The tag field for parseable.image has been updated to "v2.0.0", which aligns with the new major release. Please ensure that the new image version is available in your container registry.

helm/Chart.yaml (2)

3-3: Enhanced chart description.

The description has been updated to "Helm chart for Parseable - Fast Observability on S3" to provide clearer context about the chart’s functionality. Verify that this new phrasing aligns with the overall product messaging.

---

5-6: Version bump confirmation.

Both the version and appVersion fields have been updated to 2.0.0, consistent with the image tag change and representing a major release. This update should trigger corresponding downstream processes (e.g., CI/CD pipelines or upgrade procedures).

index.yaml (1)

37-37: Timestamp update verification.

The new entry shows a created timestamp of "2025-04-03T15:07:32.083415477+05:30". Please verify that this timestamp is generated as part of your release process and is consistent with the intended release schedule.