[WIP] db_instance: allow_major_version_upgrade conflicts replicate_source_db #7013
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.
Changes proposed in this pull request:
allow_major_version_upgrade
as conflicting withreplicate_source_db
This is at least true for PostgeSQL RDS read replicas. The following error is reported when
allow_major_version_upgrade=true
on a PostgreSQL read replica when attempting to modifyengine_version
.I'm unsure of behavior with MySQL, MariaDB, MSSQL or Oracle engines, or how to limit the
ConflictsWith
scope to a conditional onengine
.Alternatively, setting
allow_major_version_upgrade
could set theForceNew
flag for the PostgreSQL engine andreplicate_source_db
, but I'm unsure how to express that logic.TODO: Check and update acceptance tests.
Output from acceptance testing:
Enhancement/Bugfix to a Resource
Vendor additions