You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
After upgrading the AWS provider from v3.58.0 to v3.64.0 Terraform should have maintained the existing cdc_start_position value for the replication task instead of setting that to null.
Error: InvalidParameterValueException: Invalid CdcStartPosition format
status code: 400, request id: 35cc8d70-1267-4326-babd-f8b3367303fd
on main.tf line 385, in resource "aws_dms_replication_task" "cdc_user":
385: resource "aws_dms_replication_task" "cdc_user" {
Steps to Reproduce
terraform apply
upgrade provider from v3.58.0 to v3.64.0
terraform apply
Important Factoids
Probably the task has been stopped/resumed after the task was created by terraform and no changes were detected in the plans since the option was not supported until v3.62.0.
anGie44
added
bug
Addresses a defect in current functionality.
and removed
needs-triage
Waiting for first response or review from a maintainer.
labels
Feb 22, 2022
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
After upgrading the AWS provider from v3.58.0 to v3.64.0 Terraform should have maintained the existing
cdc_start_position
value for the replication task instead of setting that tonull
.Actual Behavior
terraform plan
outputterraform apply
fails with the error belowSteps to Reproduce
terraform apply
terraform apply
Important Factoids
Probably the task has been stopped/resumed after the task was created by terraform and no changes were detected in the plans since the option was not supported until v3.62.0.
References
cdc_start_position
#21201The text was updated successfully, but these errors were encountered: