-
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
Add data ecs_runtask #12096
Add data ecs_runtask #12096
Conversation
Hello guys that is my first contribution in GO and to terraform. The ideas of this PR is replace this:
For a terraform resource:
I have 2 questions api docs |
Closing as stale due to inactivity. |
+1. I think it would be really useful to re-open and consider this PR. |
Would also really love to reopen this PR. Seems like a lot of people would fine this useful |
There is no "clean" way to run a one-off ECS task via terraform, until a PR like [this one](hashicorp/terraform-provider-aws#12096) is merged. This change adds a "rails db:migrate" task, along with a (commented-out) service. Uncommenting the service and running `terraform apply` will cause ECS to start running this task. > The task will run multiple times, so any task you run using this method **must** be idempotent. Once you have confirmed that the task has run successfully, comment out the service and re-run `terraform apply` so that ECS stops launching it. This sucks, and there are [cleaner ways to achieve this](hashicorp/terraform-provider-aws#1703 (comment)) but this was the easiest to get running, and I've spent enough time shaving this particular yak.
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #1703
Release note for CHANGELOG:
Output from acceptance testing: