-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS DMS Tasks fails with "Invalid task settings JSON" #9200
Comments
ghost
mentioned this issue
Jul 2, 2019
github-actions
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
Jul 2, 2019
@ewbankkit Sounds familiar. Think it can be closed |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
ghost
locked and limited conversation to collaborators
Nov 1, 2019
breathingdust
removed
the
needs-triage
Waiting for first response or review from a maintainer.
label
Sep 17, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by Alien2150 as hashicorp/terraform#21918. It was migrated here as a result of the provider split. The original body of the issue is below.
Hello there,
I noticed something odd when using the terraform dms task module. So what I could see is that terraform apply for the first time will create the task. Rerunning it afterwards with the same settings will crash it.
Terraform Version
Terraform Configuration Files
Debug Output
If needed i can provide it
Crash Output
https://gist.github.com/Alien2150/37ff7c67089f1872ce234c09bc456747
Expected Behavior
Tasks should not have be changed.
Actual Behavior
Tasks assumes the task-settings have changed. And wants to recreate and fails with the error message.
Steps to Reproduce
terraform init
terraform apply
terraform apply
The text was updated successfully, but these errors were encountered: