added metadata for aws-nova

[sfahad1414]

Summary by CodeRabbit

• New Features
  • Added support for AWS Nova AI models, enhancing configuration options.
  • Introduces new parameters for temperature, maximum tokens (extended up to 5120), model selection, top probability, and customizable stop sequences.

[coderabbitai]

Walkthrough

The changes add a new "aws-nova" section to the AI models schema in metadata/llm_metadata.yml. This section defines properties such as temperature, max_tokens, model, top_p, and stop, with specified types, default values, and constraints. Notably, max_tokens now supports a maximum of 5120 tokens. Additionally, the description for frequency_penalty has been updated, maintaining consistency with existing model definitions.

Changes

File	Change Summary
metadata/llm_metadata.yml	Added new "aws-nova" section with properties: temperature (number, default 0.0, range 0.0–2.0), max_tokens (integer, default 300, range 5–5120), model (string, default "bedrock/converse/us.amazon.nova-lite-v1:0", enum specified), top_p (number, default 0.0, range 0.0–1.0), stop (array, maxItems 4). Updated frequency_penalty description.

Possibly related PRs

• added Gemini metadata #1513: Introduces a similar new model configuration ("gemini") in the same file, aligning closely with the aws-nova changes.

Suggested reviewers

• hiteshghuge

Poem

Hopping along through the code,
With a twitch and a nod,
New aws-nova sprouts,
Bringing tokens that shout,
A rabbit’s joy in every line 🍃🐇
Code and carrots in harmony combine!

---

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>, 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. (Beta)
• @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.

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)

metadata/llm_metadata.yml (1)

239-239: Add Newline at End of File
Static analysis flagged that there is no newline character at the end of the file. Adding a newline will improve compatibility with various tools.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 239-239: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d71acd1 and 03b2715.

📒 Files selected for processing (1)

• metadata/llm_metadata.yml (1 hunks)

🧰 Additional context used

🪛 YAMLlint (1.35.1)

metadata/llm_metadata.yml

[error] 239-239: no new line character at the end of file

(new-line-at-end-of-file)

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

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Python CI

🔇 Additional comments (2)

metadata/llm_metadata.yml (2)

199-204: Ensure Consistent Frequency Penalty Description
The updated description for the frequency_penalty property reads clearly and is consistent with how similar properties are defined in other sections.

---

205-239: AWS Nova Section Schema Looks Good
The new aws-nova section is well structured and in line with existing model definitions. Specific observations:

• The temperature property (lines 210-215) correctly uses a number type with appropriate default and constraints.
• The max_tokens property (lines 216-221) properly expands the maximum value to 5120 tokens as intended.
• The model property (lines 222-226) includes a clear default and an enum with valid values.
• The top_p property (lines 227-232) and the stop property (lines 233-239) are defined consistently with other sections.
  No issues found.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 239-239: no new line character at the end of file

(new-line-at-end-of-file)