feat: Make repl config timeouts configurable #82
Merged
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
This PR exposes the timeouts block for the aws_dms_replication_config Terraform resource
Motivation and Context
In my team's work, we have found that Serverless Replications can take longer than the resource's default 60m timeout to become healthy. So we end up in a bad Terraform state, where TF creates the Replication, times out creating the config and leaves the resource in a tainted state that we need to clean up. Ideally, this change will allow TF to fully create Replication Config resources without timing out.
Breaking Changes
Changes are optional and non-breaking
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request