-
-
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: update parameter group to fix name vs. name_prefix #304
fix: update parameter group to fix name vs. name_prefix #304
Conversation
dbcd26a
to
ab0d63c
Compare
v2.25.0 has been just released. |
I didn't have much time to see why CI failed all of sudden so as quick fix, I've ended up to pin |
BTW: Just tried to bump to latest version with option:
my run ends with:
Comment: coalesce() supports default values, maybe should be used here? |
hi @atrakic, I have opened a PR that should do two things that have been identified:
I've updated the two examples to show and validate this |
@bryantbiggs Yes, after second attempt I was able to bump to latest with:
|
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
parameter_group
sub-module and instead use a variable flag to determine whether or not to use a unique prefix on the name; this matches what was done in theoption_group
sub-modulevar.identifier
from sub-module and instead rely onvar.parameter_group_name
providedexample/option-groups
->option/groups
to test/validate changes to option and parameter groups outside of creating RDS instancesMotivation and Context
name
versusname_prefix
for the sub-modules as well as the root module (subnet group will be next and last update required now that option group is done + this PR)Relates to #121
Breaking Changes
yes; albeit minor since again, parameter groups can be re-created without disruption (
create_before_destroy
is used here)For users who are looking to upgrade, they will need to perform the following changes if they wish to forgo the re-creation:
If using without the name-prefix for parameter groups:
terraform state mv module.<your_module_name>.db_parameter_group.this_no_prefix module.<your_module_name>.db_parameter_group.this
How Has This Been Tested?
examples/*
projectsexamples/groups
directory