fix: update subnet group to fix name vs. name_prefix #312
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
var.identifier
from sub-module and instead rely onvar.name
name
orname_prefix
in the subnet sub-module; currently defaultsname_prefix
Motivation and Context
name
versusname_prefix
for the sub-modules as well as in the root module. This is a continuation of fix: update option group to fix name vs. name_prefix and conditional creation for postgresql #302 and fix: update parameter group to fix name vs. name_prefix #304 which should now conclude the standardization ofname
andname_prefix
for the sub-modulesCloses #42
Closes #48
Closes #121
Closes #209
Closes #223
Closes #250
Closes #280
Closes #290
Breaking Changes
No - other than description change below, there should be no changes for users
For users who are looking to upgrade, they should perform the following change if they wish to avoid any changes:
How Has This Been Tested?
examples/*
projectsexamples/complete-mysql
and `examples/complete-postgresql projects