resource/aws_db_instance: Prevent error when using snapshot_identifier with multi_az enabled and sqlserver engine #5613
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.
When calling
RestoreDBInstanceFromDBSnapshot
and attempting to enableMultiAZ
withEngine
set to SQL Server,MultiAZ
must be set to disabled since the API requiresBackupRetentionPeriod
and that parameter is not available for the initial API call. We then fix the configuration by callingModifyDBInstance
afterwards during creation.Previously:
Fixes #5594
Changes proposed in this pull request:
multi_az
withsnapshot_identifier
andengine
set tosqlserver*
, remove parameter or catch specific error and requireModifyDBInstance
API call afterwardsModifyDBInstance
is being called during resource creation, always setApplyImmediately
totrue
to prevent need for double apply.Output from acceptance testing: