Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Updates supported resource types (2) #857

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

udondan
Copy link
Owner

@udondan udondan commented Jan 11, 2025

Added resources:

  • AWS::AppConfig::Deployment
  • AWS::CustomerProfiles::EventTrigger

Summary by CodeRabbit

  • New Features
    • Added support for two new AWS resource types:
      • AWS::AppConfig::Deployment
      • AWS::CustomerProfiles::EventTrigger

Copy link

coderabbitai bot commented Jan 11, 2025

Walkthrough

This pull request updates the SUPPORTED_RESOURCE_TYPES constant in the src/supported_resource_types.rs file by adding two new AWS resource types: AWS::AppConfig::Deployment and AWS::CustomerProfiles::EventTrigger. The change increases the array size from 1105 to 1107 entries, expanding the list of supported resource types without modifying any existing entries.

Changes

File Change Summary
src/supported_resource_types.rs Increased SUPPORTED_RESOURCE_TYPES array size from 1105 to 1107 by adding 2 new resource types: AWS::AppConfig::Deployment and AWS::CustomerProfiles::EventTrigger

Possibly related PRs


📜 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 153fbdd and c076de2.

📒 Files selected for processing (1)
  • src/supported_resource_types.rs (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/supported_resource_types.rs
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Automerge CI

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b679231 and 153fbdd.

📒 Files selected for processing (1)
  • src/supported_resource_types.rs (3 hunks)
🧰 Additional context used
🪛 GitHub Actions: Test
src/supported_resource_types.rs

[error] 1-1109: Large array defined as const. The array contains 1107 elements which is considered too large for a const definition. Consider using 'static' instead of 'const' for this array.

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Automerge CI
🔇 Additional comments (1)
src/supported_resource_types.rs (1)

52-52: LGTM! New resource types added correctly.

The following AWS resource types have been added in alphabetical order:

  • AWS::AppConfig::Deployment
  • AWS::CustomerProfiles::EventTrigger

Let's verify that these are valid AWS CloudFormation resource types:

Also applies to: 260-260

✅ Verification successful

Verification successful: Both resource types are valid AWS CloudFormation resources

  • ✓ AWS::AppConfig::Deployment
  • ✓ AWS::CustomerProfiles::EventTrigger
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the new resource types are valid AWS CloudFormation resource types

# Test: Check AWS documentation for these resource types
curl -s "https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-deployment.html" -o /dev/null -w "%{http_code}\n"
curl -s "https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-customerprofiles-eventtrigger.html" -o /dev/null -w "%{http_code}\n"

Length of output: 306

@@ -1,4 +1,4 @@
pub const SUPPORTED_RESOURCE_TYPES: [&str; 1105] = [
pub const SUPPORTED_RESOURCE_TYPES: [&str; 1107] = [
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix the pipeline failure by using 'static' instead of 'const'.

The pipeline indicates that using const for large arrays (1107 elements) may cause performance issues.

Apply this diff to resolve the pipeline failure:

-pub const SUPPORTED_RESOURCE_TYPES: [&str; 1107] = [
+pub static SUPPORTED_RESOURCE_TYPES: [&str; 1107] = [
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
pub const SUPPORTED_RESOURCE_TYPES: [&str; 1107] = [
pub static SUPPORTED_RESOURCE_TYPES: [&str; 1107] = [
🧰 Tools
🪛 GitHub Actions: Test

[error] 1-1109: Large array defined as const. The array contains 1107 elements which is considered too large for a const definition. Consider using 'static' instead of 'const' for this array.

@udondan udondan force-pushed the resource-type-updates branch from 153fbdd to c076de2 Compare January 12, 2025 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant