-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: default to AWS provided option and parameter groups when not creating nor providing #308
fix: default to AWS provided option and parameter groups when not creating nor providing #308
Conversation
…ating nor providing
I did a plan with my local project and confirmed that it works as I expected before this latest release. |
thanks @bondezbond ! |
main.tf
Outdated
@@ -2,10 +2,10 @@ locals { | |||
create_db_subnet_group = var.db_subnet_group_name == "" ? var.create_db_subnet_group : false | |||
db_subnet_group_name = coalesce(var.db_subnet_group_name, module.db_subnet_group.this_db_subnet_group_id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bryantbiggs: It looks like similar change is required for db_subnet_group_name
as function coalesce
fails with same error due to 'module.db_subnet_group.this_db_subnet_group_id' parameter which does not has a value yet in case I try to create db_subnet_group.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point, the subnet changes were coming down the pipe as well till this little snafu (master...bryantbiggs:fix/subnet-group) - I can put this back to the original though for the time being in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated in c66fc9c
I just cloned your fork and attempted to run the complete_postgresql example and it's still throwing the same error:
|
ya I'm not sure @sayerrrr what the error might be, I spun up both the |
@bryantbiggs interesting, let me see what i can come up with - appreciate your time! |
Will this fix also include the use-case of using the module to setup an RDS replica? The error I'm currently getting is related to the mentioned issues #303 #305 #307:
I'm setting up a replica using the following options in my module: module "dis_replica" {
source = "terraform-aws-modules/rds/aws"
version = "2.25.0"
identifier = "${local.dis_master_db_identifier}-replica1"
apply_immediately = true
auto_minor_version_upgrade = false
# Source database. For cross-region use this_db_instance_arn
replicate_source_db = module.dis_primary.this_db_instance_id
engine = local.dis_engine
engine_version = local.dis_engine_version
instance_class = local.dis_instance_class
allocated_storage = local.dis_allocated_storage
max_allocated_storage = local.dis_max_allocated_storage
storage_type = local.dis_storage_type
storage_encrypted = local.dis_storage_encrypted
port = local.dis_port
# Username and password must not be set for replicas
username = ""
password = ""
vpc_security_group_ids = [module.vpc.default_security_group_id, aws_security_group.dis_rds.id]
maintenance_window = local.dis_maintenance_window
backup_window = local.dis_backup_window
performance_insights_enabled = local.dis_performance_insights_enabled
performance_insights_retention_period = local.dis_performance_insights_retention_period
deletion_protection = true
# disable backups to create DB faster
backup_retention_period = 0
# Not allowed to specify a subnet group for replicas in the same region
create_db_subnet_group = false
create_db_option_group = false
create_db_parameter_group = false
} |
@siozosdr yes |
@bryantbiggs Please let me know when you think it is ready to be merged. |
we should be all set @antonbabenko - did one last check using |
Let's see! 🤞 v2.26.0 has been just released. |
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. |
Description
Motivation and Context
Closes #303
Closes #305
Cloess #307
Breaking Changes
How Has This Been Tested?
examples/*
projectsexamples/complete-mysql
andexamples/complete-postgresql
+ added 2nd set of configs to both to prove this case here where a default group will be used by AWS when none is provided