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

fix: Ensure that passing values for option group with PostgreSQL does not cause errors #467

Conversation

bryantbiggs
Copy link
Member

Description

  • Ensure that passing values for option group with PostgreSQL does not cause errors

Motivation and Context

Breaking Changes

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@@ -93,7 +93,7 @@ module "db_instance" {
vpc_security_group_ids = var.vpc_security_group_ids
db_subnet_group_name = local.db_subnet_group_name
parameter_group_name = local.parameter_group_name_id
option_group_name = local.option_group
option_group_name = var.engine != "postgres" ? local.option_group : null

Choose a reason for hiding this comment

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

Why would you null it when you can define an actual option group? (honest question)

Copy link
Member Author

Choose a reason for hiding this comment

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

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithOptionGroups.html

PostgreSQL does not use options and option groups. PostgreSQL uses extensions and modules to provide additional features. For more information, see Supported PostgreSQL extension versions.

Choose a reason for hiding this comment

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

Thanks!

@@ -8,6 +8,7 @@ on:

env:
TERRAFORM_DOCS_VERSION: v0.16.0
TFLINT_VERSION: v0.44.1
Copy link
Member Author

Choose a reason for hiding this comment

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

Using a version avoids a few GitHub API calls which is currently causing issues with some workflows. Looks like they might have changed some of the rates, not sure why this is now an issue but just using a version seems to resolve this

Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

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

LGTM since it fixes the issue.

@bryantbiggs bryantbiggs merged commit 696acbb into terraform-aws-modules:master Jan 3, 2023
@bryantbiggs bryantbiggs deleted the fix/postgres-option-group branch January 3, 2023 13:22
antonbabenko pushed a commit that referenced this pull request Jan 3, 2023
### [5.2.3](v5.2.2...v5.2.3) (2023-01-03)

### Bug Fixes

* Ensure that passing values for option group with PostgreSQL does not cause errors ([#467](#467)) ([696acbb](696acbb))
@antonbabenko
Copy link
Member

This PR is included in version 5.2.3 🎉

@github-actions
Copy link

github-actions bot commented Feb 3, 2023

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

create_db_option_group = true is avoiding the creation of a Postrgres instance
3 participants