Skip to content

Conversation

posquit0
Copy link
Member

Summary

Update resource group configuration to use object-based pattern.

Changes

  • Update module version from ~> 0.10.0 to ~> 0.12.0
  • Replace individual resource_group_* variables with single object variable
  • Update all references to use var.resource_group.* structure
  • Add resource_group output to each module

Modules Updated

  • nacl
  • nat-gateway
  • route-table
  • security-group
  • subnet-group
  • vpc

Test Plan

  • Review variable changes
  • Verify resource-group module references are correct
  • Check outputs are properly formatted

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @posquit0, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the management of AWS resource groups within several core modules. By refactoring how resource group configurations are defined and referenced, it enhances the modularity and maintainability of the codebase. The changes aim to provide a more consistent and intuitive way to interact with resource group settings across the affected modules.

Highlights

  • Module Version Update: The internal resource-group module version has been updated from ~> 0.10.0 to ~> 0.12.0 across all affected modules.
  • Variable Refactoring: Individual resource_group_enabled, resource_group_name, and resource_group_description variables have been consolidated into a single, object-based resource_group variable for a more structured configuration.
  • Reference Updates: All internal references within the modules have been updated to utilize the new var.resource_group.attribute structure, ensuring consistency with the refactored variable.
  • New Output Added: A new resource_group output has been introduced in each updated module to expose details of the managed resource group, such as its ARN and name.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions github-actions bot added 💾 nacl This issue or pull request is related to nacl module. 💾 nat-gateway This issue or pull request is related to nat-gateway module. 💾 route-table This issue or pull request is related to route-table module. 💾 security-group This issue or pull request is related to security-group module. 💾 subnet-group This issue or pull request is related to subnet-group module. 💾 vpc This issue or pull request is related to vpc module. size/XL Extra Large size issue or PR. labels Sep 10, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the resource group configuration across several modules to use a more modern object-based pattern. This is a great improvement for consistency and maintainability. My review includes suggestions to simplify the implementation of the new resource_group output in each module for better readability. I also noticed a minor misplacement of a variable definition in one of the modules.

Comment on lines +33 to +44
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

Comment on lines +72 to +83
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

Comment on lines +126 to +137
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

Comment on lines +69 to +80
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

Comment on lines +299 to +310
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

Comment on lines +350 to +364
variable "resource_group" {
description = <<EOF
(Optional) A configurations of Resource Group for this module. `resource_group` as defined below.
(Optional) `enabled` - Whether to create Resource Group to find and group AWS resources which are created by this module. Defaults to `true`.
(Optional) `name` - The name of Resource Group. A Resource Group name can have a maximum of 127 characters, including letters, numbers, hyphens, dots, and underscores. The name cannot start with `AWS` or `aws`. If not provided, a name will be generated using the module name and instance name.
(Optional) `description` - The description of Resource Group. Defaults to `Managed by Terraform.`.
EOF
type = object({
enabled = optional(bool, true)
name = optional(string, "")
description = optional(string, "Managed by Terraform.")
})
default = {}
nullable = false
}

Choose a reason for hiding this comment

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

medium

For better organization and consistency with other modules in this PR, this resource_group variable block should be placed under the # Resource Group section header, around line 325. It's currently placed at the end of the file.

Comment on lines +289 to +300
value = merge(
{
enabled = var.resource_group.enabled && var.module_tags_enabled
},
(var.resource_group.enabled && var.module_tags_enabled
? {
arn = module.resource_group[0].arn
name = module.resource_group[0].name
}
: {}
)
)

Choose a reason for hiding this comment

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

medium

The use of merge here makes the code a bit complex to read. You can simplify this by using a ternary operator for the entire value, which is more direct and readable.

  value = (var.resource_group.enabled && var.module_tags_enabled) ? {
    enabled = true
    arn     = module.resource_group[0].arn
    name    = module.resource_group[0].name
  } : {
    enabled = false
  }

@posquit0 posquit0 merged commit 93a6bb5 into main Sep 10, 2025
17 checks passed
@posquit0 posquit0 deleted the feat/improve-resource-group-usage branch September 10, 2025 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

💾 nacl This issue or pull request is related to nacl module. 💾 nat-gateway This issue or pull request is related to nat-gateway module. 💾 route-table This issue or pull request is related to route-table module. 💾 security-group This issue or pull request is related to security-group module. 💾 subnet-group This issue or pull request is related to subnet-group module. 💾 vpc This issue or pull request is related to vpc module. size/XL Extra Large size issue or PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant